Add direct APIs for Http.Sys extensions currently using IHttpSysRequestInfoFeature

We previously only exposed a ROM<byte> for IHttpSysRequestInfoFeature since underlying data structure in Http.Sys were still subject to change. Given that the underlying API is now stable (as I understand based on the Windows API docs), we should replace this feature in favor of a feature with typed-data.

Checklist to track exposing the data via explicit APIs:

• HttpRequestInfoTypeAuth,
• HttpRequestInfoTypeChannelBind,
• HttpRequestInfoTypeSslProtocol,
• HttpRequestInfoTypeSslTokenBindingDraft and HttpRequestInfoTypeSslTokenBinding
• HttpRequestInfoTypeRequestTiming
  • HttpSys https://github.com/dotnet/aspnetcore/pull/48218
  • IIS https://github.com/dotnet/aspnetcore/pull/48663
• HttpRequestInfoTypeTcpInfoV0 and HttpRequestInfoTypeTcpInfoV1 (V1 is a superset of V0)
• HttpRequestInfoTypeRequestSizing
• HttpRequestInfoTypeQuicStats

[NGloreous]

My understanding is that enum members would never be removed, only added for backwards compatibility. The members shouldn’t be considered chronologically order (it is the case for the first few when this was first added but others have been added since which occur out of order chronologically).

[msftbot[bot]]

We’ve moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.