Mid-stream I/O errors are silently ignored in TCP proxy and other network filters

[PiotrSikora]

Mid-stream I/O errors (e.g. Connection reset by peer) are never propagated out of transport sockets, and connections terminated because of those errors are closed exactly the same way as in case of a clean shutdown, which results in silent truncation, and the information about that is not available in neither %CONNECTION_TERMINATION_DETAILS%, %UPSTREAM_TRANSPORT_FAILURE_REASON%, nor %RESPONSE_FLAGS%.

While some L7 network filters can detect premature connection termination because of truncated and/or missing frames, L4 network filters (e.g. TCP proxy) are completely lost here.

cc @alyssawilk @antoniovicente @ggreenway @kyessenov

[PiotrSikora]

See #13941 for my attempt at fixing it.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.