[EKS] [request]: ec2-scheduler

### 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**
To use ec2 as fargate uses ECR.

**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?**
Currently, this feature doesn't depend on AWS, but building a custom kubernetes scheduler is a bit hard for me.
In short, I want to automatically create an ec2 instance based on pod requests as it works in binding with Fargate Profiles. Optionally we could specify instance type, security groups and subnets using annotations.
It might resolve all node depending issues with Fargate keeping everything stateless(there are a lot of requests adding support of securityContext options), so there will be no need to create NodeGroup for each deployment and pods will be able to use privileged functionality.

**Are you currently working around this issue?**
I'm dealing with Fargate limits and thinking of creating an ec2-scheduler myself.

**Additional context**
Anything else we should know?

**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 entry points are named. Start by reviewing the requested EKS/Fargate behavior and Kubernetes scheduler documentation, then clarify the scope for creating EC2 instances from pod requests and handling instance types, security groups, subnets, and annotations; done requires an agreed design and implementation plan.

Written by the indexing model from the issue text.