Fix daily / CI failures by bumping the Test Framework to 1.4.2.Beta9 and migrating package type configuration property

[michalvavrik]

Summary

As a follow up of the quarkusio/quarkus#39295 we should adapt our tests. While fallback config interceptors are in place, we need to sync properties set with how the framework detects them and works with them.

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

[michalvavrik]

run tests

[michalvavrik]

@gtroitsk OCP JVM failures are not related because OTel condition seems to fail as test is badly written (I'll provide fix in a separate PR) and Infinispan I can't see related to changes listed in the quarkus-qe/quarkus-test-framework#1069.

[michalvavrik]

Ah, there is a difference in the traces after all, but it's not related. Will need to look it up.

[michalvavrik]

Found it, caused by quarkusio/quarkus#39534. I'll open new PR.

[gtroitsk]

@michalvavrik can you analyse please what caused failures in OperatorOpenShiftInfinispanObjectsIT?

[michalvavrik]

@michalvavrik can you analyse please what caused failures in OperatorOpenShiftInfinispanObjectsIT?

The question is, how is it relevant to the changes here? There is so many failures I need to fix, this is not on the top of my list. I run OperatorOpenShiftInfinispanObjectsIT from my computer and I can reproduce the failure on the current main, which means that it's not related to this PR.

I plan to debug it tomorrow and open upstream issue over class cast exception.

[gtroitsk]

@michalvavrik can you analyse please what caused failures in OperatorOpenShiftInfinispanObjectsIT?

The question is, how is it relevant to the changes here? There is so many failures I need to fix, this is not on the top of my list. I run OperatorOpenShiftInfinispanObjectsIT from my computer and I can reproduce the failure on the current main, which means that it's not related to this PR.

I plan to debug it tomorrow and open upstream issue over class cast exception.

In that case it is ok, thank you for testing and confirmation. I will merge this PR

[gtroitsk]

Thank you!

[rsvoboda]

I think this is wrong, fast-jar,legacy-jar,uber-jar,mutable-jar should be the allowed only ones @michalvavrik

[michalvavrik]

You are right, luckily it's just a README, I'll create a fix.