[ECR] - TAG option for ECR Cross Region and Account Replication

### 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**
TAG option for ECR Cross Region and Account Replication

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We are using TAG in promoting repositories between AWS accounts and Regions based on the RELEASES we have ( We are using the Environment based to use Filter option)

**Are you currently working around this issue?**
Manually filtering out the RELASE based artifacts and replicating using pipeline.

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Start by reading the ECR Cross Region and Account Replication request and its stated pipeline workaround. Determine the intended TAG-based filtering behavior for RELEASE artifacts across accounts and Regions, then confirm the requirement with maintainers before proposing a design; done means the requested replication selection is supported.

Written by the indexing model from the issue text.