Commit Message: This builds on #19831 , adding an attempt to use http filter methods to deploy flow-control, so we can pause generation of admin output until clients are ready for it.

This is not ready yet -- @alyssawilk has explained to me how to get the flow-control to work

• use high-watermark callback to set a bit in the filter to avoid sending more data
• use low-watermark callback to clear the above bit and send another chunk, and then queue up a callback for the next chunk (assuming high-water callback is not called).

This pattern should also be in the http cache filter and also the Router, though the latter is a lot more complex.
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

Request variables

Key	Value
ref	3863e20ae1f2c43f465fd1d3e1b8c1a88ead8bd2
sha	dbba968
pr	31087
base-sha	c82c083
actor	@jmarantz
message	admin: apply flow control via high/low watermarks...
started	1708613836.044857
target-branch	main
trusted	false

Container image/s (as used in this CI run)

Envoy version (as used in this CI run)