Remove IKestrelTrace

[JamesNK]

Fixes #31581

Yeet IKestrelTrace and associated implementations.

TODO:

• Seal KestrelTrace
• Remove virtual methods from KestrelTrace
• Remove commented out files

I will do the same for SocketsTrace and QuicTrace in future PRs.

[davidfowl]

Why do we still have kestrel trace?

[JamesNK]

It wraps a bunch of differently named loggers:

aspnetcore/src/Servers/Kestrel/Core/src/Internal/Infrastructure/KestrelTrace.cs

Lines 13 to 28 in cd8e890

	internal partial class KestrelTrace : IKestrelTrace
	{
	protected readonly ILogger _generalLogger;
	protected readonly ILogger _badRequestsLogger;
	protected readonly ILogger _connectionsLogger;
	protected readonly ILogger _http2Logger;
	protected readonly ILogger _http3Logger;
	public KestrelTrace(ILoggerFactory loggerFactory)
	{
	_generalLogger = loggerFactory.CreateLogger("Microsoft.AspNetCore.Server.Kestrel");
	_badRequestsLogger = loggerFactory.CreateLogger("Microsoft.AspNetCore.Server.Kestrel.BadRequests");
	_connectionsLogger = loggerFactory.CreateLogger("Microsoft.AspNetCore.Server.Kestrel.Connections");
	_http2Logger = loggerFactory.CreateLogger("Microsoft.AspNetCore.Server.Kestrel.Http2");
	_http3Logger = loggerFactory.CreateLogger("Microsoft.AspNetCore.Server.Kestrel.Http3");
	}

It could be split out into BadRequestsLog, Http2Log, etc, but I think a centralized type that ensures the right logger is used for each log message seems worthwhile.

[Tratcher]

Very happy to see these test trace classes gone.