Share AmiTags in DistributionConfiguration

### 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**
I would like the AmiTags attribute specified in the DistributionConfiguration resource to be shared with the distributed AMIs.

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
My team is attempting to restrict launching EC2 instance to AMIs with a particular tag, similarly to this [AWS blog post](https://aws.amazon.com/premiumsupport/knowledge-center/restrict-launch-tagged-ami/), and we would like ImageBuilder to make and share these AMIs. I've noticed that when you define AmiTags, these are added to the AMIs in the account where the AMI is built, but they don't appear for the shared AMIs in the downstream accounts.
If they could be present when an AMI is distributed, that may save us quite a bit of operational overhead to manage this restriction.

**Are you currently working around this issue?**
We've only brainstormed so far, but the potential workaround would be a lambda function to copy tags from built AMIs to their shared counterparts.

**Additional context**
N/a.

**Attachments**
N/a

Start by reviewing the DistributionConfiguration AmiTags behavior and the linked AWS blog post on restricting launches to tagged AMIs. Compare tags on AMIs built in the source account with those on shared AMIs in downstream accounts. Done means the requested tags are present on distributed AMIs, with the behavior confirmed across the relevant account flow.

Written by the indexing model from the issue text.