feat(versioning/redhat): Support for Red Hat release versioning

[Churro]

Changes

This PR adds support for the versioning pattern used by Red Hat-maintained container images. This enables updates for ubi8-minimal, rhel7, ubi9/perl-532 and further images that follow this versioning.

Workaround patterns are added for all container libraries which are maintained exclusively by Red Hat and which only images that follow this versioning concept. So, no false positives should occur, as all images in these paths indeed use this versioning (Yes, I verified that). Note: the absence of trailing slashes in some cases is totally on purpose, as there is e.g. ubi7-minimal but also ubi7/ubi-minimal.

Red Hat version definitions (e.g.. 8.0-7) consist of:

• the version of the main component, whereas major is mandatory, minor and patch optional
• optionally a hyphen followed by release information
• the version of Red Hat's release, described as an integer and optionally followed by a timestamp, e.g. 2.4-195.1655305687 (Apache httpd 2.4)

Test repositories:

• https://github.com/Churro/renovate-rhel/pulls (= fork of the minimal repro repo from Renovate doesn't update Docker Images from Red Hat Registry #15781)
• https://github.com/Churro/renovate-redhat-versioning/pulls (= many more tests with expected versions in comments)

Implementation Notes

#15781 (comment) mentioned a promising RegEx, which, unfortunately, only works in very specific cases:

• It requires a build version to be specified, i.e., with ubi-minimal:8.6 -> "skipReason": "invalid-value"
• It only works if there is a minor update available, e.g. ubi-minimal:8.5-218 -> 8.6-751
  • This would even be wrong because 8.6-751 is not the newest version

It is possible to make this RegEx more "flexible", e.g. like this:
"versioning": "regex:^(?<major>\\d+)(?:\\.(?<minor>\\d+))?(?:[-\\.](?<patch>\\d+))?(?:[-\\.](?<build>\\d+))?(?:\\.(?<prerelease>\\d+))?$"
-> this will recognize the "major release version" in patch and handle an occasional "minor release version" in build. This is still spurious because with ubi9/ubi-minimal, patch versions were introduced and then this doesn't work anymore. In addition, precedence is not handled correctly because higher minor release versions should trigger an update (e.g. 1-19 -> 1-19.1655193074).

The solution implemented in this PR works with ubi8, ubi9 and any other image following this versioning. Tested also with many different version variations (https://regex101.com/r/MKZaMQ/1).

Context

Closes #15781

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[viceice]

otherwise LGTM

[HonkingGoose]

Docs are good to go.

[renovate-release]

🎉 This PR is included in version 32.105.0 🎉

The release is available on:

• GitHub release
• 32.105.0

Your semantic-release bot 📦🚀