[EKS] [request]: Remove requirement for EC2 permissions on aws-node VPC CNI daemon

### 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**
aws-node daemon that runs as part of VPC CNI plugin should not need EC2 API permissions on every worker node.

**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?**
Today, the VPC CNI plugin includes a daemon that needs to run on every worker node, which makes EC2 API calls to configure networking reachability for pods. IAM Roles for Service Accounts help solve the problem of adding the EC2 API permissions to each worker node and instead to just the daemonset pod itself. But a better option would be to separate out the ipamd functionality into a separate controller that doesn't need to run on every node.

No repository files or tests are named. Start by understanding the aws-node VPC CNI daemon, its ipamd functionality, the EC2 API calls, and the daemonset pod described in the issue; done would mean defining and implementing a separate controller that removes EC2 permissions from every worker node.

Written by the indexing model from the issue text.