Backport of UI/bugfix/UI format allow fqdn into release/1.21.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #22779 to be assessed for backporting due to the inclusion of the label backport/1.21.

The below text is copied from the body of the original PR.

---

Description

We've deployed a new version of consul server (upgraded from 1.21.2 to 1.21.3) and we've lost the ability to see on the UI the list of URLs for certain services that instead of IP Addresses they are FQDN from AWS services.
This might be related to the IP Validation introduced under #22468

Testing & Reproduction steps

1. On an already created cluster, try to register a service with address equals to an FQDN

consul services register \
-http-addr=https://consul-server.kube-system:8501/ \
-address=random-instance-sadgadsfgad.eu-north-2.es.amazonaws.com \
-port=443 \
-id=random-instance \
-name=random-instance \
-ca-file=/consul/tls/ca/tls.crt \
-ca-path=/consul/tls/ca/

2. Check the service URL on the UI

Links

• URLs are not displayed on UI when using FQDN instead of IP Address #22568
• [UI] format ipv6 address to collapsed form #22468

PR Checklist

• updated test coverage
• external facing docs updated
• appropriate backport labels added
• not a security concern

PCI review checklist

• I have documented a clear reason for, and description of, the change I am making.

• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.

• If applicable, I've documented the impact of any changes to security controls.

  Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

---

Overview of commits

• 6df6707

[github-team-consul-core-pr-approver]

Auto approved Consul Bot automated PR