Is your feature request related to a problem?

Gateway-API is someday going to replace ingress.
Currently we only have BETA support for routes, which are not connected to much of the chart processes

Describe the solution you'd like

We should implement both routes AND gateway objects and ensure feature parity with ingress

We might want to abstract away gateway and routes into a single top-level key. Like is currently done with ingress.

Describe alternatives you've considered

.

Additional context

The nice thing about it, is that its cut into multiple objects.

• GatewayClass (cluster-wide gateway settings)
• Gateway (the entrypoint definition)
• Routes (comparable with ingress, linking entry points to svcs with domain names)

There are also some consequences of this, the most important one is that we need to "abstract" away things like hostname-fetching first.
As we cannot rely on going over all ingresses anymore to fetch hostnames, as those could also be defined on httpRoutes en tcpRoutes

Somewhat depends on: #31880

https://gateway-api.sigs.k8s.io/concepts/api-overview/
https://gateway-api.sigs.k8s.io/guides/migrating-from-ingress/
https://docs.nginx.com/nginx-gateway-fabric/overview/gateway-architecture/

I've read and agree with the following

• I've checked all open and closed issues and my request is not there.
• I've checked all open and closed pull requests and my request is not there.