[EKS] [request]: Managed Node Groups - Container health check along with EC2 health for 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**
Possibility of considering Container health check along with EC2 health for underlying ASG

**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 AutoScaling Group considers EC2 health check, taking container health as well brings in more control.
This help during scale in operations and also helps to consider instances unhealthy where containers are not running as expected. If it is possible to achieve, ASG can select the instances with pods other than running state to terminate during any scale-in operations.

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

The request concerns EKS managed node groups and the underlying Auto Scaling Group, but names no repository files, tests, or implementation entry points. Start by researching how container and EC2 health are exposed to EKS and Auto Scaling, then define the supported scale-in behavior and its validation criteria.

Written by the indexing model from the issue text.