Fix HttpLoggingMiddleware Request/Response bodies logging in case of stream being closed by a subsequent middleware

[ExtraClock]

Fix HttpLoggingMiddleware Request/Response bodies logging in case of stream being closed by a subsequent middleware (#61489)

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Preserve buffer contents until it is consumed by the HttpLoggingMiddleware

Description

Fixes #61489

When the subsequent middleware closes request/response stream, the BufferingStream calls Reset which leads to an empty body being logged.

The request stream might be closed if the subsequent middleware follows the ContentLength header to sense the end of the stream (instead of reading it to the end).

The response stream might be closed without any additional preconditions, just because the subsequent middleware decided to do so.

A real-life example of such a middleware is CoreWCF BasicHttpBinding: inputStream.Close, _outputStream.Close

[dotnet-policy-service]

Thanks for your PR, @@ExtraClock. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[ExtraClock]

@dotnet-policy-service agree