[EKS/Fargate] [request]: Fargate profile tag propagation

### 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**
When adding a Fargate Profile in EKS you are able to add tags to it. However, it seems that these tags do not propagate to billing. My assumption was that if you tagged a Fargate Profile, all Fargate containers which run in EKS would then have the relevant tag in their corresponding AWS billing line item.

If this is not the case, what are those tags used for? And is there possibly a preferred way to tag Fargate containers running in EKS?

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Trying to differentiate between different Fargate tasks / containers using the tags in the Fargate Profiles.

**Are you currently working around this issue?**
Currently remains unsolved

No repository files, tests, or entry points are named in issue #803. Start by investigating how EKS Fargate Profile tags relate to billing line items and task or container tagging; done means the propagation behavior and a preferred tagging approach are established and clearly documented.

Written by the indexing model from the issue text.