[ECR] [request]: Reject images that don't have the specified tag pattern

### 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**
What do you want us to build?
Reject images with tags outside a specified standard, for example:
- starting with (prefix)
- ending with
- REGEX

**Which service(s) is this request for?**
This could be Fargate, ECS, EKS, ECR

ECR

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

The objective is to guarantee the standard of tags used in the repository without depending on the "goodwill" of a CI pipeline or the creator. Without a tag pattern, lifecycle rules based on tag names are inefficient.

**Are you currently working around this issue?**
How are you currently solving this problem?

I mitigated with the use of EventBridge+Lambda but they cause technical confusion because the image is deleted after being submitted and the communication to the user/automation depends on him having signed an SNS topic... This procedure also causes complexity in the implementation of the CI pipelines

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

I tried to perform this block using AWS Config but I couldn't understand how to do it or if it's possible to do it with it

**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 reviewing the ECR request and its examples for prefix, suffix, and regex tag patterns. The work is complete when ECR can reject images whose tags do not match a specified pattern without relying on EventBridge, Lambda, or CI pipelines; no repository files or tests are named.

Written by the indexing model from the issue text.