[EKS] [request]: auto mode: Allow access to managed-control-plane component logs

### 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

**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?**
Successfully debugging auto-mode issues like #2486 is challenging without access to logs related to components AWS is managing for us in the managed control-plane. Taking operational overhead off my plate is great, but I am responsible for IAM and SG related build which can have subtle errors when using advanced features like IAM paths and permission boundaries. Having customer access to logs can reduce the cycle-time for issue resolution (even in the cases where support needs to be pulled in).

**Are you currently working around this issue?**
N/A

**Additional context**
N/A

**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.)

The issue names EKS Auto Mode and managed control-plane logs but provides no repository files, tests, or implementation entry point. Start by clarifying which managed components and access path are intended; done would mean customers can access the relevant logs for debugging, including IAM and security-group-related cases.

Written by the indexing model from the issue text.