IssueTracker

Currently, cleanup policies support filtering by prefixes, but there is no documented support for regular expressions to match more complex tag structures. This limitation makes it difficult to differentiate between production and development artifacts when tags follow a structured format, such as v1.0.0 for production and v1.0.0-RC-* for release candidates.

For example, a typical requirement is to clean up only pre-release artifacts while preserving production versions. However, since cleanup policies only allow filtering by prefixes, there is no way to exclude production versions while targeting only RC artifacts.

Proposed Solution:
* Allow users to define cleanup policy filters using regular expressions instead of just simple prefixes.
* Provide documentation and examples for commonly used patterns (e.g., filtering pre-release tags using v[0-9]+\.[0-9]+\.[0-9]+-.*).
* Alternatively, introduce suffix-based filtering as an additional option to help distinguish between versions.

Use Case Example:
Tags:
* v1.0.0 → Should not be deleted (production)
* v1.0.0-RC-1 → Should be deleted (release candidate)
* v2.0.0 → Should not be deleted
* v2.0.0-RC-2 → Should be deleted

Current Workarounds & Limitations:
* Users must restructure their CI/CD tagging strategy to fit within prefix-based filtering.
* This is not ideal, as it requires significant refactoring across pipelines.