[EKS] [request]: Provide kube-proxy replacement in VPC CNI

### 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**
Provide kube-proxy replacement in VPC CNI

**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?**
With support of network policy by vpc cni ref https://github.com/aws/containers-roadmap/issues/1478, looking for kube-proxy replacement which would help free up some more resources in worker nodes. Introduction of ebpf would help https://github.com/aws/containers-roadmap/issues/1478#issuecomment-1196977159

**Are you currently working around this issue?**
Using kube-proxy addon

Start by reading the referenced VPC CNI network-policy issue and its linked comment, then compare that context with the current kube-proxy addon workaround. The issue does not identify files, tests, or an implementation entry point; done would require a maintainer-defined kube-proxy replacement scope and acceptance criteria for EKS.

Written by the indexing model from the issue text.