[EKS][request]: Add support for tagging ENIs provisioned for worker nodes

**Tell us about your request**

We would like to have support for propagation of custom tags to ENIs being used by worker nodes.

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, if you add Resource Tags for Network Interfaces in a Launch Template and use this Launch Template to create/update a Managed Nodegroup, the new Launch Template created by created by EKS workflow does not copy these ENI resource tags and hence any custom tags are not propagated to the underlying ENIs.

**Are you currently working around this issue?**

There is no workaround currently. The only brute approach is to tag ENIs manually but that hardly helps in automating the process as nodes may get recycled and ENIs ay be detached and reattached.

We have already tried:

1. aws autoscaling create-or-update-tags CLI command [1].

2. using eksctl to apply tags

eksctl create nodegroup --managed --tags --cluster --region

but even with this, tags were not applied to ENIs.

[1] https://docs.aws.amazon.com/cli/latest/reference/autoscaling/create-or-update-tags.html

It would be great if this capability could be automated.

The issue concerns EKS managed node groups, Launch Templates, and tags on worker-node ENIs; it does not name a repository file or test entry point. Start by reviewing the referenced AWS CLI documentation and the listed eksctl command, then define support for propagating those tags to ENIs and verify that tags survive node recycling.

Written by the indexing model from the issue text.