[EKS] [request]: EKS Auto Mode supports local-zone nodes

### 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**
Support for local-zone nodes.

**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 require compute resources regionally closer to a service utilizing the compute. This is a requirement to reduce latency, and it appears from further discussions with AWS engineer members it is unavailable at this time.

**Are you currently working around this issue?**
How are you currently solving this problem?
Not enabling Auto Mode, and instead using Karpenter.

**Additional context**
Anything else we should know?
It wasn't obvious the reason the region isn't supported since there are no logs indicating node provisioning errors. I noticed there is a ticket related to managed control plane logging, which would be quite helpful. https://github.com/aws/containers-roadmap/issues/2492

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

No repository files, tests, or code entry points are identified in the request. Start by reviewing EKS Auto Mode's support for local-zone nodes and the related managed control plane logging issue, #2492. Done means Auto Mode supports local-zone nodes and the limitation or provisioning failure is visible to users.

Written by the indexing model from the issue text.