[EKS] [request]: Add ability to provide custom tags for ASG created from managed node group

### 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**
Please, add ability, to provide custom tags used by auto scaling group, created from managed node group. Cluster autoscaler is able to determine for example node labels, taints and also resources from this tags.

**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?**
I'm trying to divide EKS workload based on worker node labels / taints. Some node groups are expensive and we like to use them only for specific tasks. But cluster autoscaler cannot scale them, as they are using specific label and taint, which we are using for our pods, to prevent running unwanted workload on this nodes.
Cluster autoscaler can scale even this node groups, when he knows, which one labels / taints will they have. It is reading them from ASG tags.

**Are you currently working around this issue?**
Currently, we are using directly defined ASG, instead of worker node groups, with cluster-autoscaler hint tags.

Start by reviewing how EKS managed node groups create their auto scaling groups and how Cluster Autoscaler reads ASG tags; the issue names no repository files, tests, or entry points. Done means users can provide custom labels, taints, and resource tags for the ASG created from a managed node group, allowing Cluster Autoscaler to scale it.

Written by the indexing model from the issue text.