[ECS] [Complaince]: AWS Config integration to ecs resources

### 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**
AWS Config is a great config complaince checking tool, but unfortunately it doesn't support ecs resources of task definitions, ecs services, ecs clusters etc,..

This can heavily benefit our current infrastructure where multiple owners manage multiple clusters/services etc,.. it would be great to setup complaince checks via AWS Config itself. although the request is for ECS we are also looking forward to extending aws config to EKS resources as well

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

**Are you currently working around this issue?**
currently we are making our own listeners for change streams and our own cron system for validating all resources at once, essentially we are making our own `AWS Config`

This is a broad roadmap request for AWS Config support covering ECS, EKS, and ECR resources, including task definitions, services, and clusters. No repository files, tests, or implementation entry points are named; first clarify the intended service scope and acceptance criteria before identifying where work would begin.

Written by the indexing model from the issue text.