[EKS] [request]: Support EKS Auto components individually

### 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'd like to be able to use EKS Auto components on their own, specifically in this case the compute management via a managed _Karpenter_ instance (see #1792). Ideally some of the constraints for individual components could be lifted when not running in full "auto" mode.

**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?**
I want to be able to manage compute via Karpenter without needing to manually run compute as is required today (no I don't want to use Fargate).

**Are you currently working around this issue?**
Running compute via ASGs.

**Additional context**
n/a

**Attachments**
n/a

No repository files, tests, or entry points are identified. Start by reviewing the EKS Auto components context and linked issue #1792; done would mean enabling compute management through a managed Karpenter instance without requiring manually run compute or Fargate.

Written by the indexing model from the issue text.