Enable Gateway API and Envoy Gateway by default
<!--
NOTICE: This Issue tracker is for the GitLab Helm chart, not the GitLab Rails application.
Support: Please do not raise support issues for GitLab.com on this tracker. See https://about.gitlab.com/support/
-->
## Summary
In the past months we invested heavily into Envoy Gateway and Gateway API support in our chart. Our previous default, ingress-nginx is now officially retired and archived.
## Notes
The Gateway Controller we install across test instances may conflict with each other. Just like the Ingress controllers.
## Acceptance Criteria
- [x] GitLab chart deploys Envoy Gateway and Gateway API resources by default
- [x] ingress-nginx is disabled by default but remains available as a fallback for folks who want to do the migration later
- [x] Ingress'es remain available but are disabled by default
- [x] GitLab chart and Operator pipelines use the new default where suitable; Review environment that need additional changes to use Gateway API can remain on Ingress for now.
issue