Log bytes for HTTP/1.1 parsing failures

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

HTTP/1.1 request formats are not well standardized and clients often bend/break the spec. This can cause Kestrel to reject the request with a 4XX. When this happens, it can be hard for the app to understand exactly what was wrong with the request.

### Describe the solution you'd like

When a parsing failure is encountered, we should report the raw bytes from the request buffer. This will bypass the common debugging step of "please capture a network trace" and is even better than a network trace because it can capture the decrypted content when using TLS.

### Additional context

Where should this be reported? In the BadRequest event?