[EKS] [kube-proxy addon]: Add tolerations config

### 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**
Add tolerations config to the kube-proxy addon (like the ebs-csi). The kube-proxy supports this, but the config in aws eks addon does not.

**Which service(s) is this request for?**
EKS / kube-proxy addon

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Taint a nodes to only run core workload on them.

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

Start with the issue request and compare the existing EKS ebs-csi addon configuration with the kube-proxy addon configuration. Determine where addon configuration is defined and how kube-proxy tolerations are exposed; done means users can configure tolerations for the kube-proxy addon so it can run on tainted nodes.

Written by the indexing model from the issue text.