[ECR] [request]: Allow exclusion of prefixes for lifecycle policy rules

### 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**
Allow exclusion of tag prefixes for lifecycle policy rules

**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 promote our images from preproduction to production. We may create a number of preproduction images, but ultimately only release a few of those to production. We would like to use a lifecycle policy to clean up the preproduction images but there is no way to exclude those with production tags as well.

For example, an image has the following tags:

`8c96f0598f74e5f9c61fe8dcefe7c11732ee3b30, release-4-5-2-8c96f059-463320462, v4.5.2`

A lifecycle rule targeting the `release` prefix will clean up this image.

What we need is a rule for images that have a `v` prefix, and a rule for images that have a `release, not v` prefix.

**Are you currently working around this issue?**
We are not currently running a lifecycle policy on these images

**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.)

This is an AWS ECR lifecycle-policy feature request, and the payload names no repository files, tests, or implementation entry points. Start by reviewing the ECR lifecycle-policy behavior described in the request and the service's existing policy constraints. Done means ECR can exclude production-tagged images while applying cleanup to matching preproduction tags.

Written by the indexing model from the issue text.