[ECS] [Events]: Add resource tags to ECS events

### 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**
It would be very nice if ECS event's structure had aws resource tags included to it. It has a lot of information about container definitions of task (if we are speaking about Task State Change events) but not tags, which makes processing of these events feature limited for us.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Our tech team has a lot of sub-teams working for different branches of business and we tag our resources accordingly to make sure all AWS resources are tagged according to system it is backing and team that maintains this system.
Processing ECS events might also be done using these tags so they could be delivered to different notification channels based ob resource tags.

**Are you currently working around this issue?**
Currently, we are doing the same thing, but with making event "enrichment" with invoking ECS API with Lambda, that receives original event.

No repository files or tests are identified in the issue. Start by reviewing the requested ECS Task State Change event structure and the current Lambda-based enrichment workaround; done means ECS events include the relevant AWS resource tags without requiring that enrichment step.

Written by the indexing model from the issue text.