Add direct APIs for Http.Sys extensions currently using IHttpSysRequestInfoFeature

[shirhatti]

We previously only exposed a ROM 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 Add IHttpSysRequestTimingFeature to support accessing http.sys timing info #48218
  • IIS Support IHttpSysRequestInfoFeature and IHttpSysRequestTimingFeature in IIS in proc server #48663
• HttpRequestInfoTypeTcpInfoV0 and HttpRequestInfoTypeTcpInfoV1 (V1 is a superset of V0)
• HttpRequestInfoTypeRequestSizing
• HttpRequestInfoTypeQuicStats

[Tratcher]

Which feature? This one was an abstraction over about 4 native extensions. I don't expect this one to go away, more than we would just add others.

[adityamandaleeka]

Triage: we should add a new feature and not add to the existing one.

See #3842, this should be a shared feature between the two implementations.

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.