[service] [request]: eks manage/unmanage nodegroup tags doesn't get propagated to resources (ec2/ebs)

**Tell us about your request**
We try to do our AWS costing with AWS tag, however eks manage nodegroup doesn't get the tag propagated from launchtemplate
When launch eks new nodegroup, the EC2 instance and EBS volume shall get proper tagging from launchtemplate or equivalence.
Without this our costing estimation are all wrong.
Without this our monitoring can't base on AWS tag.

**Which service(s) is this request for?**
EKS nodegroup

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We need to solve our costing problem and monitoring problem with basic AWS tag like all other resources.

**Are you currently working around this issue?**
Manually tagging it. it is time consuming and may paste it (human error) wrong tag and all downstream are all wrong.

**Additional context**
This should be a day 1 feature, don't you think?

**Attachments**
Found out this from AWS support, https://docs.aws.amazon.com/eks/latest/userguide/eks-using-tags.html#tag-resources

Start with the linked AWS EKS resource-tagging documentation and verify how managed nodegroup tags are currently handled. Done means tags from the launch template, or an equivalent mechanism, propagate correctly to the EC2 instances and EBS volumes created for the nodegroup.

Written by the indexing model from the issue text.