Handle naming conflicts for deployed resources

[lgadban]

kgateway version

n/a

Is your feature request related to a problem? Please describe.

When a Gateway is created, Kgateway dynamically deploys the resources needed for the proxy which will implement the Gateway, such as Deployment, Service, etc. These resources will have the same name as the Gateway.

Users may have resources already existing in the namespace with the same name as the Gateway in which case there is a conflict.

Describe the solution you'd like

We should define a suitable UX for this situation

Describe alternatives you've considered

While we can provide error reporting etc. when this situation occurs, the "correct" fix would be for users to not name their Gateway in a way to clash with existing resources.

Additional Context

No response