Problems with AddressResolver on ipv6 stack

### Version

5.0.0

### Context

There is a problem in KubeServiceState when a WebSocket is created to a Kubernetes API with an ipv6 stack.
In particular, the WebSocket fails to establish connection after the TLS handshake is correctly performed.
After some tries, I discovered that if environment variable "KUBERNETES_SERVICE_HOST" is enclosed in square brackets:
"fd00:eccd:22:ffff::5555:1" -> "[fd00:eccd:22:ffff::5555:1]"
then connection is correctly performed and KubeServiceState is able to get notified about changes in "endpoints" configuration.

Therefore there should be some code within the WebSocket framework that is not able to correctly handle "ipv6:port" schema
(i.e. To avoid problems with the ":" in the ipv6 for an uri schema, just enclose it with square brackets)

### Steps to reproduce

To reproduce just deploy a Kubernetes cluster with ipv6 stack.
In particular service for api server should be something like:
`kubectl get svc -n default

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP fd00:eccd:22:ffff::5555:1 443/TCP 224d
`

### Do you have a reproducer?

_No response_