Create subcategories for better filtering Kestrel logs

[fvoronin]

Splitting Kestrel logs into multiple subcategories from general "Microsoft.AspNetCore.Server.Kestrel":

1. Microsoft.AspNetCore.Server.Kestrel (current category): ApplicationError, ConnectionHeadResponseBodyWrite, ApplicationNeverCompleted, RequestBodyStart, RequestBodyDone, RequestBodyNotEntirelyRead, RequestBodyDrainTimedOut, ResponseMinimumDataRateNotSatisfied, InvalidResponseHeaderRemoved, HeartbeatSlow.
2. Microsoft.AspNetCore.Server.Kestrel.BadRequests: ConnectionBadRequest, RequestProcessingError, RequestBodyMinimumDataRateNotSatisfied.
3. Microsoft.AspNetCore.Server.Kestrel.Connections: ConnectionAccepted, ConnectionStart, ConnectionStop, ConnectionPause, ConnectionResume, ConnectionKeepAlive, ConnectionRejected, ConnectionDisconnect, NotAllConnectionsClosedGracefully, NotAllConnectionsAborted, HeartbeatSlow, ApplicationAbortedConnection.
4. Microsoft.AspNetCore.Server.Kestrel.Http2: Http2ConnectionError, Http2ConnectionClosing, Http2ConnectionClosed, Http2StreamError, Http2StreamResetAbort, HPackDecodingError, HPackEncodingError, Http2FrameReceived, Http2FrameSending, Http2MaxConcurrentStreamsReached.
5. Microsoft.AspNetCore.Server.Kestrel.Http3: Http3ConnectionError, Http3ConnectionClosing, Http3ConnectionClosed, Http3StreamAbort, Http3FrameReceived, Http3FrameSending.

Fixes #30301

[davidfowl]

One failing test:

[xUnit.net 00:00:04.14]     Microsoft.AspNetCore.Server.Kestrel.InMemory.FunctionalTests.HttpConnectionManagerTests.CriticalErrorLoggedIfApplicationDoesntComplete [FAIL]

[fvoronin]

One failing test:

[xUnit.net 00:00:04.14]     Microsoft.AspNetCore.Server.Kestrel.InMemory.FunctionalTests.HttpConnectionManagerTests.CriticalErrorLoggedIfApplicationDoesntComplete [FAIL]

Thanks.
Haha, i miss out that cause it's run #if !DEBUG.

[fvoronin]

Oh, i dont know why this test failed

[xUnit.net 00:00:28.41]     Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http3ConnectionTests.InboundStreams_CreateMultiple_ConnectionError(streamId: 3, name: "decoder") [FAIL]

It does not corelated with code changes in this PR.

[Tratcher]

The H3 tests are still new and a bit unstable, I've re-run them.

[halter73]

The same test failed on the second attempt. So it's either really flaky or something changed. I've started a third run to collect more data.

[halter73]

Never mind. The same test didn't fail. It was ProjectTemplates tests failing on attempt 2 which are very flaky. I was looking at the new ".NET Helix Build Analysis" view. While it's super convenient, it doesn't appear to update on retries.

[halter73]

Nit: While the heartbeat does loop over connections, this log is usually an indicator of threadpool starvation.

Suggested change

	_heartbeatSlow(_connectionsLogger, now, heartbeatDuration, interval, null);
	_heartbeatSlow(_generalLogger, now, heartbeatDuration, interval, null);

[fvoronin]

Applied

[halter73]

Thanks! This looks great.

[halter73]

Thanks @fvoronin! (I also accidently put this in the commit message 🤣 )