[EKS] [Bug]: Tag Trunk-ENI

### 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**
What do you want us to build?
Tagging the Trunk-ENI thats created via aws-vpc-resource-controller-k8s.

**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?**
We are using a specific tag on our resources to calculate costs. Unfortunately the trunk-eni created for eks is not tagged.

**Are you currently working around this issue?**
I'm currently running a lambda function every hour to tag based on the attached ec2-instance.

Start by reviewing the EKS trunk-ENI flow and the aws-vpc-resource-controller-k8s context described in the issue, then compare it with the current Lambda workaround. Done means the trunk ENI receives the required cost tag when it is created, without relying on the hourly Lambda.

Written by the indexing model from the issue text.