Request for information/support on http2 transport enablement in conformance test

[pramodrj07]

What would you like to be added:
Need support for http2 in conformance test specifically the "roundtripper" package

Why this is needed:
To overcome limitation of just using http1 in the conformance test as the upstream backend host might just support only http2
https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/utils/roundtripper/roundtripper.go#L111

**Additional Details **:
From the initial investigation, it looks like we cannot pass the custom HTTP client into the default round tripper implementation. If there is an alternate way to achieve this, I would like to be redirected there.

[gauravkghildiyal]

Will passing in an http2.Transport through the CustomDialer in a Request be sufficient for your use case?

gateway-api/conformance/utils/roundtripper/roundtripper.go

Lines 41 to 52 in 6efcfdf

	type Request struct {
	URL url.URL
	Host string
	Protocol string
	Method string
	Headers map[string][]string
	UnfollowRedirect bool
	CertPem []byte
	KeyPem []byte
	Server string
	CustomDialer http.RoundTripper
	}

[ibilalkayy]

Checkout this PR that I just sent

[shaneutt]

This sounds good.

/triage accepted

It would be nice to have this for GA, but it doesn't appear to need to block it so we'll leave it off the v1.0.0 milestone.

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted