[EKS] [Request]: Support for all ENIs on EKS windows Nodes

### 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**
What do you want us to build?
Support all ENIs on a EKS windows workernode so that pods can consume all IPs supported by an instance types.
**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?

Currently, Windows worker nodes support one elastic network interface per node. The number of pods that you can run per Windows worker node is equal to the number of IP addresses available per elastic network interface for the node's instance type, minus one.

This poses a limitation on running multiple pods on a single EKS windows workerNode.

**Are you currently working around this issue?**
No workaround for this is available.

Start by reviewing the EKS Windows worker-node networking behavior described in the issue, focusing on the one-ENI limitation and how pod IP capacity is calculated for an instance type. Determine what support for all ENIs would require and how success would be measured: Windows nodes should use all supported ENIs and expose the corresponding pod capacity.

Written by the indexing model from the issue text.