[EKS] [request]: Configure Cluster API nodes ENIs

### 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**
I would like to have the option to configure the ENIs attached to the Cluster API 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?**
We use Tailscale / Wireguard for secure connections into our VPC. We deploy a subnet router which forwards requests to all resources inside our VPC. We would like to preserve the clients (Tailscale) IP address so that we can do more granular access control (based on IP) on the level of our services. For that we disable the src/dst check on the subnet router and don't NAT the packets flowing through it.

Unfortunately the ENIs attached to the Cluster API nodes have src/dst check enabled and therefore won't accept packets from the subnet router with the origin clients IP address. It would be nice to configure the ENIs as part of the EKS cluster creation. For us configuring the src/dst check would be sufficient but maybe there are other scenarios where one would like to configure other ENI parameters.

**Are you currently working around this issue?**
The current solution is NAT'ting the packets but that blocks us from the aforementioned IP level access control further down the line.

Start by reviewing the EKS cluster creation flow and how ENIs are attached to Cluster API nodes. The request is complete when cluster creation can configure the attached ENIs, including disabling source/destination checks, without requiring NAT; the issue mentions no repository files or tests to run.

Written by the indexing model from the issue text.