[EKS] [request]: Enable Configuration to Set the Number of Pods to 110

### 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**
Currently, EKS Auto mode has a default limit on the number of pods running per node. I would like to increase this limit to 110 pods per node.

**Which service(s) is this request for?**
EKS Automode

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Each node has a default number of pods it can handle, depending on the node type, but I want to configure it to run 110 pods.
I ran the following
kubectl set env daemonset aws-node -n kube-system ENABLE_PREFIX_DELEGATION=true
kubectl describe daemonsets.apps -n kube-system aws-node | grep ENABLE_PREFIX_DELEGATION ENABLE_PREFIX_DELEGATION: true

**Are you currently working around this issue?**
I cannot currently work around this issue.

**Additional context**
None

**Attachments**
None

Start with the EKS Auto mode pod-per-node limit and the kubectl commands for the aws-node DaemonSet shown in the issue. Determine whether a supported configuration entry point exists for setting the limit to 110 pods per node; done means the setting is supported and its behavior is validated.

Written by the indexing model from the issue text.