e2e tests are not capable of detecting if they are using vsphere or a different cloud platform.

In that case, once e2e is being executed, it will try to assess that a DNS Record was properly created for vsphere platforms and fail.

This story intends to:

• create a vsphere + static e2e cluster
• Install MetalLB (check with rhn-support-hongli how it is done on our pipelines and follow a similar approach)
• Verify how the DNS management is made for Gateway API (unmanaged, probably)
• Change our e2e tests (https://github.com/openshift/cluster-ingress-operator/blob/56e29778bc2168c324e55ddecd2d838a3ea287bf/test/e2e/gateway_api_test.go#L71) to not wait for DNS to be ready in case of non cloud (aka non GCP and non AWS tests)
• Change the tests to inject DNS resolution instead on these cases, but pointing to the LoadBalancer IP