IIS HTTP/2 headers only response with END_STREAM flag on headers

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe the bug

A gRPC user is hosting their web app with IIS. They have noticed that a headers-only gRPC response (over HTTP/2) sends a HEADERS frame and an empty DATA frame with the END_STREAM flag. This goes against the gRPC HTTP/2 spec, which says the HEADERS frame should have the DATA frame.

### Expected Behavior

IIS sends a HEADERS-only response with the END_STREAM flag in the HEADERS frame.

Note that this Kestrel has the correct behavior.

### Steps To Reproduce

_No response_

### Exceptions (if any)

_No response_

### .NET Version

_No response_

### Anything else?

_No response_