Gateway API conformance: Run conformance report generation in CI

[sunjayBhatia]

Gateway API has an experimental version of the test suite that can be run to generate a conformance report, see:

• https://github.com/kubernetes-sigs/gateway-api/blob/main/geps/gep-917.md
• https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/utils/suite/experimental_suite.go
• https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/experimental_conformance_test.go

We should generate the conformance report in CI so we can publish it to the Gateway API repo (and in the future to whatever other conformance reporting infrastructure might exist), e.g. kubernetes-sigs/gateway-api#2192

Open for discussion where/when we should run the reporting and exactly the output, my initial thoughts:

• Should output a file containing the conformance report YAML (possibly in addition to printing the output to the action logs)
• Run on pushes to main and release tags
• Reported Contour component version for non-release versions should use the commit SHA
• Don't run on PRs, just run the normal test suite

[sunjayBhatia]

spike branch on what things might look like: https://github.com/sunjayBhatia/contour/blob/6bf46b64005439d8d4010cfe4d6b41683a82bacc/test/conformance/gatewayapi/gateway_conformance_test.go#L53-L89

[sunjayBhatia]

Still various issues to work out:

• Cumbersome experimental conformance reporting suite UX  kubernetes-sigs/gateway-api#2205
• Experimental conformance suite: Extended skipped tests not being reported kubernetes-sigs/gateway-api#2206

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

• Mark this Issue as fresh by commenting
• Close this Issue
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

• Mark this Issue as fresh by commenting
• Close this Issue
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack