Run api gateway conformance tests in consul-k8s repository

[sarahalsmiller]

Changes proposed in this PR:

• Run gateway-k8s conformance tests against consul-k8 native implementation of the gateway API as a github action by building a docker image of the control plane and loading it onto a kind cluster
• Tests currently run but fail due to changes that need to be made in the API Gateway code itself

How I've tested this PR:

• CI kicks off and runs as expected

How I expect reviewers to test this PR:

• CI runs

Checklist:

• [ X ] Tests added
• CHANGELOG entry added

  HashiCorp engineers only, community PRs should not add a changelog entry.
  Entries should use present tense (e.g. Add support for...)

[andrewstucki]

Tagging @curtbushko to see if this should go here or in our workflows repo. In this case we're running OSS as the target Consul for the conformance tests, so wondering it we don't need the extra safety/configurability of the private runners and this can stay in-repo?

[andrewstucki]

Also @sarahalsmiller the conformance tests fork are roughly ~1000 commits behind upstreams main. Wondering if we can attempt to target the upstream repo now and target these feature sets:

	SupportReferenceGrant,
	SupportGateway,
	SupportGatewayClassObservedGenerationBump,
	SupportHTTPRoute,
	SupportHTTPRouteQueryParamMatching,
	SupportHTTPRouteMethodMatching,
	SupportHTTPRoutePathRewrite,

As mentioned in Slack, the current repo doesn't ever set the "Ready" status, just "Programmed" as "Ready" has been marked deprecated/for future use (the updated tests look for "Programmed").

[sarahalsmiller]

Closing to move over into consul-k8s-workflows. Will also look at targeting the upstream repo.