[ECR] [Feature Request]: ECR repo Chained 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**
Currently, we can set up [automatic repo replication](https://docs.aws.amazon.com/AmazonECR/latest/userguide/replication.html) from a source account/region to a destination account/region. But if the replication is not passed further to more accounts as a chain.
For example, what we can do now is : Account A -> Account B, Account A -> Account C.
What we want to achieve is: Account A -> Account B -> Account C

**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?**
Since we have the pipeline Dev -> Test -> Staging -> Prod, we do not want Dev to directly work with more higher environment.

**Are you currently working around this issue?**
We can only replicate repo from one account to multiple accounts.

**Additional context**

**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 with the AWS ECR replication documentation linked in the issue and compare the documented one-source-to-multiple-destinations behavior with the requested Account A → Account B → Account C chain. No repository files, tests, or implementation entry points are identified; done would require an agreed product design and documented support for chained replication.

Written by the indexing model from the issue text.