Expose HTTP.sys kernel response buffering control for HttpListener on Windows

[karimsalem1]

This PR adds an opt-in AppContext switch to enable kernel response buffering in HttpListener (Windows implementation only). When enabled, the flag HTTP_SEND_RESPONSE_FLAG_BUFFER_DATA is set on all calls to HttpSendHttpResponse and HttpSendResponseEntityBody (consistent with Win32 docs). This mirrors the behavior for setting the HttpSysOptions.EnableKernelResponseBuffering flag in ASP.NET HTTP.sys code.

Motivation in issue #123425.

Sample usage:

AppContext.SetSwitch("System.Net.HttpListener.EnableKernelResponseBuffering", true);

using var listener = new HttpListener();
listener.Prefixes.Add("http://localhost:8080/");
listener.Start();

Console.WriteLine("Listening...");
while (true)
{
    var context = await listener.GetContextAsync().ConfigureAwait(false);
    _ = Task.Run(() => HandleRequestAsync(context));
}

Notes:

• No public API changes
• Default behavior remains unchanged
• Since API is internal, tests use reflection to validate flag behavior.
• Added dedicated Windows-only test classes for HttpListener and HttpResponseStream, and consolidated existing Windows-only tests there for consistency.

TODO: add manual validation repro showing perf improvements using this feature

Thanks @ManickaP for all the help!

[dotnet-policy-service]

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[jkotas]

No public API changes

AppContext switches are de-facto public APIs, just a different kind.

[ManickaP]

Please use DisposeAsync if you're invoking an async method. It's an extension from https://github.com/dotnet/runtime/blob/main/src/libraries/Common/tests/System/Net/RemoteExecutorExtensions.cs

We were hitting timeouts from thread pool starvation on limited CI machines due to Dispose here doing sync-over-async.

TLDR explanation: dotnet/arcade#14807

[ManickaP]

One comment otherwise LGTM. I'll await the manual validation results.

Thanks!