[EKS] [Add-Ons]: consistent configuration options across aws provided addons (and add missing ones for kube-proxy)

### 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 see consistent configuration parameters across aws provided eks add-ons.
Currently i want to configure all eks add-ons to use json logging, for which i either need to use the `additionalArgs` for a given sidecar container OR the `loggingFormat` properties for the affected container of a add-on (ebs-csi-driver).

For kube-proxy both options are missing and i want to see them, as it does indeed support json logging if you specify `--logging-format=json`.

**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?**
It is hard because there is no effective option, besides adjusting the deployment after the add-on rollout. However on each update i would need to adjust it again (and remember to do so).

**Are you currently working around this issue?**
Not

**Additional context**
-

**Attachments**
AWS Support case: 173589159400126

The issue concerns EKS add-on configuration, especially kube-proxy. Start by reviewing how existing add-ons expose additionalArgs and loggingFormat; done means kube-proxy supports JSON logging and configuration options are consistent across AWS-provided add-ons. No repository files or tests are named, so locating the relevant implementation and validation is part of the work.

Written by the indexing model from the issue text.