Fix and extend release version checker

[gtroitsk]

Summary

Fixes problems with globbing and adds additional check of next-version in project.yml

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Release (follows conventions described in the RELEASE.md)
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[gtroitsk]

@michalvavrik do you want from me some examples of new added checks?

[michalvavrik]

@michalvavrik do you want from me some examples of new added checks?

we had examples last time; tbh I simply don't have time span to verify this works as expected. it would be enough for me to understand how you tested it, so that we know it works.

[github-actions]

Following jobs contain at least one flaky test: 'Linux - JVM build - Latest Version'

[gtroitsk]

@michalvavrik I made some examples

Main scenario: project.yml next-version must follow current-version

Latest pre-release 1.6.0.Beta1
[main] success
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/9995462717

[main] failure
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/9995472851/job/27627684518

Latest released 1.5.1 (has “latest” tag)
[1.5.z as latest LTS]
Success https://github.com/gtroitsk/quarkus-test-framework/actions/runs/9995636331/job/27628237024

Failure
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/9995646444/job/27628269444

Beta tag failure
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/9995659518/job/27628309994

Latest release 1.6.0
Latest published 1.5.1 (no tag)
[1.5.z as oldest LTS (1.3.z)]
Success
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/9995743522/job/27628587111

Failure
https://github.com/gtroitsk/quarkus-test-framework/actions/runs/9995757571/job/27628631130

[gtroitsk]

Plan for 1.3.z branch during backports
It requires releasing 1.3.0, so probably change https://github.com/quarkus-qe/quarkus-test-framework/releases/tag/v1.3.0.Beta31

After, the latest version should be 1.3.1 as a blank release or changed https://github.com/quarkus-qe/quarkus-test-framework/releases/tag/1.3.1.Final

What strategy do you prefer?

[michalvavrik]

Let's go with the easiest way, if we need 1.3.0 to have this check passing, it's better to do extra release than to invest more time into this task.

[github-actions]

Following jobs contain at least one flaky test: 'Linux - JVM build - Latest Version'