Test how cluster ingress operator handles DNS record creation when multiple Gateways are created with unique and overlapping hostnames, to ensure the correct DNS resolution.

Test cases:

• Create multiple Gateways that have listeners with the same hostname, as well as with differing hostnames and test DNS flow.
  Expectation:
  DNS should create separate DNSRecords for each unique hostname.

• Create a Gateway with Listeners that don't have a hostname:
  Expectation:
  No DNSRecord should be created. Requests with empty hostname value are processed as a fallback, after the least specific matches are exhausted.

• Gateway listener trying to claim a fully qualified hostname (abc.apps.<DNS config base domain>) that would match a *.apps.<DNS config base domain> ingress controller wildcard. Which endpoint tries to serve the request to abc.apps.<DNS config base domain>?
  Expectation:
  DNSRecord for abc.apps.<DNS config base domain> gets created. Traffic for the most specific match should be resolved to the gateway.

• DNSRecords handling when the associated Gateway is deleted or hostname was deleted or modified on the Gateway.
  Expectation:
  DNSRecords associated with the removed Gateway also get deleted.