[EKS] [request]: EKS self managed addons don't use ECR dualstack endpoints

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**

Self managed addon image urls, use the ipv4 only endpoints, for example:

602401143452.dkr.ecr.us-east-2.amazonaws.com/eks/kube-proxy:v1.34.0-eksbuild.2

This causes problems when running ipv6 only nodes.

**Which service(s) is this request for?**
EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
IPv6 EKS cluster.

**Are you currently working around this issue?**
Not sure yet.

**Additional context**
There is zero disadvantage to using a dualstack endpoint.

Start by reviewing how EKS self-managed addon image URLs are selected, using the example ECR URL in this issue and the IPv6-only node scenario. Done means addon image URLs use ECR dualstack endpoints so they work on IPv6-only EKS nodes.

Written by the indexing model from the issue text.