UI/bugfix/UI format allow fqdn

[lplinux]

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.

[hashicorp-cla-app]

All committers have signed the CLA.

[suresh-hashicorp]

Thank you @lplinux for the PR.
Can you also add a changelog for this? Guidelines

[lplinux]

Thank you @lplinux for the PR. Can you also add a changelog for this? Guidelines

Thanks @suresh-hashicorp . I've added the changelog.

[suresh-hashicorp]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

@lplinux CLA sign is pending. I can approve and merge after this.

[lplinux]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.

@lplinux CLA sign is pending. I can approve and merge after this.

I've signed it 3 times already. I hope this last time is the good one.
Thanks @suresh-hashicorp

[suresh-hashicorp]

LGTM! Thank you @lplinux

[hc-github-team-consul-core]

📣 Hi @suresh-hashicorp! a backport is missing for this PR [22779] for versions [1.21] please perform the backport manually and add the following snippet to your backport PR description:

<details>
	<summary> Overview of commits </summary>
		- <<backport commit 1>>
		- <<backport commit 2>>
		...
</details>