text: Title: Kubelet does not assign node address on expanded ipv6 address
  Body: ### What happened?
  
  In AWS EKS a issue was discovered in ipv6 only clusters. When nodes with expanded ipv6 address are created `2600:1f14:1d4:d101:0:0:0:ba3d` the string comparison [here](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/nodestatus/setters.go#L129) ends up comparing `2600:1f14:1d4:d101:0:0:0:ba3d` and
  `2600:1f14:1d4:d101::ba3d` and does not assign the ipv6 ip to the node object.
  
  ### What did you expect to happen?
  
  The string comparison should happen on sanitized ipv6 addess so that any different format of the ipv6 address being sent through the string works.
  
  ### How can we reproduce it (as minimally and precisely as possible)?
  
  On AWS EKS ipv6 clusters, scale the worker nodes until a worker node appears without the full 128bit ipv6 address octet. When such nodes are created, the node objects won't have internal-ip associated with them.
  
  ### Anything else we need to know?
  
  _No response_
  
  ### Kubernetes version
  
  <details>
  1.21/1.22/1.23
  ```console
  $ kubectl version
  # paste output here
  ```
  
  </details>
  
  
  ### Cloud provider
  
  <details>
  EKS
  </details>
  
  
  ### OS version
  
  <details>
  Ubuntu
  ```console
  # On Linux:
  $ cat /etc/os-release
  # paste output here
  $ uname -a
  # paste output here
  
  # On Windows:
  C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
  # paste output here
  ```
  
  </details>
  
  
  ### Install tools
  
  <details>
  
  </details>
  
  
  ### Container runtime (CRI) and and version (if applicable)
  
  <details>
  
  </details>
  
  
  ### Related plugins (CNI, CSI, ...) and versions (if applicable)
  
  <details>
  
  </details>
  