feat: allow for specifying pre-release in regex

[Spazzy757]

This PR allows for checking for pre-release specific tags

previously in the case of having a pre-release (i.e v1.0.*-rc) the git check would ignore the pre-release versions and just do the latest tag (i.e v1.0.1) which could be a different release entirely.

NOTE: My assumption is that this is only valid with wildcards as I dont think something like < v1.2.*-rc would be a valid constraint, but if this is incorrect please let me know

I am not entirely sure if this is considered a bug fix or a feature

Related Issue: https://github.com/argoproj/argo-cd/issues/18899

Related Discussion: https://github.com/argoproj/argo-cd/discussions/20595

would be great to have this patched in v2.12

Checklist:

• [x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• [x] The title of the PR states what changed and the related issues number (used for the release note).
• [x] The title of the PR conforms to the Toolchain Guide
• [ ] I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• [ ] I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• [x] Does this PR require documentation updates?
• [x] I've updated documentation as required by this PR.
• [x] I have signed off all my commits as required by DCO
• [x] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• [ ] My build is green (troubleshooting builds).
• [ ] My new feature complies with the feature status guidelines.
• [x] I have added a brief description of why this PR is necessary and/or what this PR solves.
• [ ] Optional. My organization is added to USERS.md.
• [ ] Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

[bunnyshell[bot]]

:exclamation: Preview Environment deployment failed on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

• :rocket: /bns:deploy to redeploy the environment
• :x: /bns:delete to remove the environment

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 55.06%. Comparing base (3b81d3c) to head (0c85079).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #20862 +/- ## ========================================== + Coverage 55.02% 55.06% +0.03% ========================================== Files 324 324 Lines 55413 55423 +10 ========================================== + Hits 30492 30517 +25 + Misses 22306 22295 -11 + Partials 2615 2611 -4 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.