[EKS] [Feature Request]: It doesn't support editing the conntrack from the kube-proxy add-on

### 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**
We should edit the conntrack value from the kube-proxy add-on of the eks. But the kube-proxy add-on doesn't support it. I hope I can edit that value.
```
conntrack:
maxPerCore: 32768
min: 131072
---
net.netfilter.nf_conntrack_max = 131072
```

**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?**
We did experience the maximum for the nf_conntrack parameter from the bottlerocket. Then our service wasn't working. So, we should increase the nf_conntrack value.

**Are you currently working around this issue?**
We are considering overriding the kube-proxy-config from eks configmap.

**Additional context**
N/A

**Attachments**
N/A

Start with the kube-proxy add-on configuration and the kube-proxy-config EKS ConfigMap mentioned in the issue. Trace how conntrack settings are exposed and identify the supported path for changing maxPerCore, min, and nf_conntrack_max; done means users can configure these values without an unsupported override.

Written by the indexing model from the issue text.