IHttpRequestBodyDetectionFeature for HTTP/3 GET requests

[ladeak]

IHttpRequestBodyDetectionFeature for HTTP/3 GET requests

IHttpRequestBodyDetectionFeature returns false for HTTP/3 (bodyless) GET requests

Description

• Implementation follows the HTTP/2 structure.
• Updated IHttpRequestBodyDetectionFeature to include HTTP/3 descriptions for the END_STREAM flag.
• In Http3Stream modified request body handling logic to return zero length content body instance when there endstream flag is set. It also completes the message body for empty requests, so that the RequestBodyPipe.Reader is closed (needs to be closed, so that when the stream is reused by the pool, the Pipe is reset which requires closed reader) - not sure if this is the best place to do this.
• Added unit test CanHaveBody_ReturnsFalseWithoutRequestBody to validate behavior when no request body is present.

Fixes #58753

[BrennanConroy]

It also completes the message body for empty requests, so that the RequestBodyPipe.Reader is closed (needs to be closed, so that when the stream is reused by the pool, the Pipe is reset which requires closed reader) - not sure if this is the best place to do this.

Http2Stream doesn't do this. It relies on the calling code the cleanup the MessageBody. Is there a reason this is different from the Http2Stream impl?

[ladeak]

@BrennanConroy - I will follow up on that.

[ladeak]

@BrennanConroy I addressed your concern.

[dotnet-policy-service]

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no conflicting changes have occurred, please rerun validation before merging. You can do this by leaving an /azp run comment here (requires commit rights), or by simply closing and reopening.