[EKS] [request]: add the option to override the verbosity level of kube-proxy EKS addon in the configurationSchema

### 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**
Please add the option to override the verbosity level of kube-proxy EKS addon in the `configurationSchema`

**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?**
Kube-proxy addon is deployed with a `--v=2` command argument which is a potentially high verbosity level. In our case, after enabling [Topology Aware Routing](https://kubernetes.io/docs/concepts/services-networking/topology-aware-routing/) kube-proxy is flooding the logs with a lot of messages for disabling topology-aware routing for services that do not have a good zone distribution which in our case can be a lot. This consequently causes the node to be evicted due to disk pressure which is caused by all these logs being dumped to disk. We don't want to manually edit and update the verbosity flag because the addon is enabled through IAC, specifically Terraform. Terraform has `resolve_conflicts_on_update`, which can be set to `PRESERVE` but isn't future-proof. For example, what happens if the command or the args are changed in the future and the new change is not deployed because `resolve_conflicts_on_update` is set to `PRESERVE`? That is a potential network blackout.

**Are you currently working around this issue?**
We're increasing disk size to accommodate these logs.

**Additional context**
No

Start by locating the EKS addon configurationSchema and the kube-proxy command arguments, then review how Terraform supplies addon configuration. Done means the schema exposes a supported verbosity override for kube-proxy and the requested value can be retained through addon updates without manual editing.

Written by the indexing model from the issue text.