[EKS] [request]: Managed Node Groups - Ability to modify termination policies of underlying ASG

### 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**
Ability to select the termination policies of underlying Auto Scaling Group.

**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 there are no options to customize the termination polices of underlying Auto Scaling Group while creating Node Groups.
The policies selected by Managed Node Groups(OldestLaunchTemplate, OldestInstance) might cause un-intended issues for few scenarios/work loads. So, ability to control the way AutoScaling terminate the instances during scale in operations will be more beneficial.

**Are you currently working around this issue?**
No workaround as of now.

Start by reviewing the EKS Managed Node Groups and underlying Auto Scaling Group context described in the request. Done means users can select the termination policies used during scale-in operations; the issue mentions no repository files, tests, or implementation entry points.

Written by the indexing model from the issue text.