[service] [request]: Stop nodes instead of terminate to keep image cache

### 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**
Allow stop node instance vs terminate

**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?**
When dealing with large images that have long pull times, it would be useful if you could have the option to stop the node instance vs terminating it. That way, when it scales back up the image is already in the cache, saving image pull time which can be significant.

**Are you currently working around this issue?**
There is no good workaround except shrinking image size to the extent possible, but there are objective limits to this.

**Additional context**
AKS recently introduced this feature which allows deallocate vs delete node

**Attachments**
NA

Start by reviewing the EKS node lifecycle and scaling behavior described in the request, then compare it with AKS deallocate-versus-delete behavior. Done would require an EKS-supported option to stop nodes rather than terminate them while preserving cached images and reducing subsequent image-pull time.

Written by the indexing model from the issue text.