[EKS] [Feature]: Windows IPv6 Support

### 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**

IPv6 support was added in early 2022. In the official announcement, it was noted that Windows was not supported:

> IPv6 is not supported on Windows nodes at the moment. We are currently working on adding IPv6 support to Windows.

This is still true today, per the docs

> You can't use [IP prefixes](https://docs.aws.amazon.com/eks/latest/userguide/cni-increase-ip-addresses.html) with Windows nodes. This is a requirement for using [IPv6](https://docs.aws.amazon.com/eks/latest/userguide/cni-ipv6.html), so you can't use IPv6 with Windows nodes either.

I wasn't able to find an existing issue in this repo to actually track/gauge interest in this feature, so I'm opening this one. (If I missed an issue that already exists, or if its in a different repo, please feel free to close this one out as a duplicate).

**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?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

**Are you currently working around this issue?**

I'm currently just not running Windows nodes on EKS clusters.

**Additional context**

Being able to run Windows nodes in EKS IPv6 clusters would greatly allow for wider adoption of EKS within organizations that are heavily Windows based, while not needing to burn IPv4 addresses/subnets for large scale deployments.

Start with the linked EKS IPv6 and IP-prefix documentation and the official announcement cited in the issue. Identify the Windows-node limitations and the relevant EKS/CNI entry points; done means Windows nodes can run in EKS IPv6 clusters without the documented IP-prefix restriction.

Written by the indexing model from the issue text.