[EKS] [Feature]: Allow EKS nodes to be stopped/started

### 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**
We would like the ability to configure EKS nodes to be stopped and started by scaling rather than terminated/created. This should mean nodes come on to the cluster quicker and have any data on those nodes persisted

**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?**
This problem is based on the wait time for a new node to be created and marked as ready by EKS. This could be quicker if the node was stopped/started. This should mean scaling would be quicker. We have a multi cloud approach and AKS supports this strategy. We would like feature parity with EKS

**Are you currently working around this issue?**
Not currently

**Additional context**
Nothing else. Supported on AKS and this would be useful with other vendors too

The issue concerns EKS node scaling and requests stopping and starting nodes instead of terminating and recreating them. No repository files, tests, or entry points are named, so first investigate how EKS node scaling is represented in this project and how comparable AKS behavior is handled. Done means a defined, supported way to configure EKS nodes for stop/start scaling with persisted node data and faster readiness.

Written by the indexing model from the issue text.