Fix runtime config properties recording in OpenShift

[michalvavrik]

Summary

Fixes openshift-tf-jvm-nightly and openshift-tf-native-nightly. (full disclosure: I also mentioned they can be flaky due to network blips in at least one run of great many I executed, and there was many of blocking warnings, but I suppose that would be a separate issue if repeated)

OpenShiftExtensionIT and OpenShiftDockerBuildIT are failing with Quarkus 3.8.4 (but not 3.8.3) and 999-SNAPSHOT as runtime values recorder at build time are not kept any more quarkusio/quarkus#39604. In OpenShift, runtime system properties set to mvn when we do .withProperty("quarkus.management.port", "9002") are not propagated so we need to copy them always to application properties. This behavior is IMHO correct because the change in Quarkus solved leaking of sensitive information.

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
• 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]

run tests

[michalvavrik]

run tests

[michalvavrik]

run tests

[michalvavrik]

run tests

[mjurc]

Thanks for the prompt fix.