Setup Java for JBang purposes in the Flaky test workflow

[michalvavrik]

Summary

I run test here quarkus-qe/quarkus-test-suite#2050 (because workflows are very similar and the script is same) and it seems that I need to setup Java for the JBang https://github.com/quarkus-qe/quarkus-test-suite/actions/runs/11041992883/job/30673453268. I didn't experience this locally for obvious reasons.

Same as: quarkus-qe/quarkus-test-suite#2051

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

[michalvavrik]

@rsvoboda here is a prove it works in the TS quarkus-qe/quarkus-test-suite#2050 (comment)

I realized I need to rename individual artifacts to avoid collisions in naming, so I'll rename these files:

Run gh run download $WORKFLOW_ID -n flaky-run-report-linux-jvm-latest || true
error downloading flaky-run-report-linux-native-latest: error extracting zip archive: error extracting "flaky-run-report.json": open flaky-run-report.json: file exists
error downloading flaky-run-report-windows-jvm-latest: error extracting zip archive: error extracting "flaky-run-report.json": open flaky-run-report.json: file exists

but that will be done separately because these are different workflows (let's not run CI again for this); I will try that first in the TS etc. So I suggest to proceed with this one.