Inspect API for HostnameGenerators shows incorrect DNS name on Global

[lukidzi]

Kuma Version

master

Describe the bug

If you have a MeshService on Kubernetes and check its DNS address in the GUI, you may see an incorrect address. That address is used by remote zones, but on local Kubernetes we don’t allocate a custom DNS address because we rely on the default Kubernetes DNS names.

To Reproduce

1. Deploy Global control-plane
2. Deploy Zone control-plane on Kubernetes
3. Enable MeshService Exclusive
4. Deploy demo application on k8s
5. Enter GUI of global control-pane, go to Mesh -> Services -> MeshService and select one MeshService
6. Check that Address is incorrect

Address that is correct when using from remote zones but it doesn't work on local k8s

status has empty dns name:

status:
  vips:
    - ip: 10.43.154.55
  tls:
    status: Ready
  dataplaneProxies:
    connected: 1
    healthy: 1
    total: 1
type: MeshService

Expected behavior

We should either show the local address or point to the local Kubernetes address, or make it clear that this address works from other zones but not from the local Kubernetes cluster.

Additional context (optional)

No response