HTTP/2: account for queued frames when validating WINDOW_UPDATE
When a stream is terminated, its unsent payload length is refunded back
to the connection flow control. Previously, this could increase the
flow control beyond NGX_HTTP_V2_MAX_WINDOW, if it was increased by the
client after the stream frames were queued and before the stream was
terminated. This eventually resulted in broken buffer size control in
ngx_http_v2_send_chain() followed by memory corruption and a possible
segmentation fault.
The fix is to account for the queued frames when validating a client
WINDOW_UPDATE. From the client's point of view, the queued frames
still belong to the flow control window.