[Batch] [Feature Request]: Propagation Of Launch Template Template Tags To Batch-Created Launch Template

### 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**

Propagation of Launch Template Template Tags to the Batch-created Launch Template.

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

Batch

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

When a Compute Environment is created and a Launch Template is supplied Batch will use that Launch Template as a basis and create its own Launch Template. If the supplied Launch Template has Template Tags those tags are not propagated to the new Batch-created Launch Template like the supplied Launch Template's Resource Tags are.

Some customers have requirements that every item in the environment needs to be tagged. As the Template Tags are not propagated the customer has to go back and manually apply the tags. Also if the customer has a SCP that prevents resource creation if tags are not specified this may cause creation of a Compute Environment to fail.

There doesn't seem to be way to work around this using Terraform or other systems. The feature request [here](https://github.com/aws/containers-roadmap/issues/1877) seems to be related.

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

N/A

**Additional context**

N/A

**Attachments**

N/A

The issue concerns AWS Batch Compute Environments that create Launch Templates from supplied templates. No repository files, tests, or implementation entry points are named, so first review the AWS Batch and Launch Template documentation and the related issue 1877. Done means Template Tags from the supplied Launch Template are propagated to the Batch-created Launch Template.

Written by the indexing model from the issue text.