Disable Quarkus CLI config tests on Quarkus version older than 3.13 due to breaking changes between 3.13 and 3.12

[michalvavrik]

Summary

Disabling tests introduced in #1902 to fix Windows failures and make it possible to run Quarkus CLI module with older versions.

• Improve Config CLI quarkusio/quarkus#41203 introduced breaking changes that I didn't mention
• ATM our Windows runners use the latest released Quarkus 3.12
• if anyone want to run Quarkus CLI module with older version to debug older versions, the test would fail

Please select the relevant options.

• Bug fix (non-breaking change which fixes an issue)
• Dependency update
• Refactoring
• Backport
• New scenario (non-breaking change which adds functionality)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[jedla97]

Thanks! It's disable on all "relevant" versions for main.

[rsvoboda]

ATM our Windows runners use the latest released Quarkus 3.12

Talking about Jenkins? Because I realized our GH Actions are not running CLI tests - e.g. https://github.com/quarkus-qe/quarkus-test-suite/blob/main/.github/workflows/daily.yaml#L144 @michalvavrik

[michalvavrik]

ATM our Windows runners use the latest released Quarkus 3.12

Talking about Jenkins? Because I realized our GH Actions are not running CLI tests - e.g. https://github.com/quarkus-qe/quarkus-test-suite/blob/main/.github/workflows/daily.yaml#L144 @michalvavrik

Yep, I meant AWS, our GH Windows runners are not running Quarkus CLI because there is no way to determine if this CLI test is starting a dev service or not. We would need to declare it on every test (which is acceptable).

[rsvoboda]

ah, forgot about containers and dev services pains :/