Fix QuarkusCliConfigEncryptIT for Windows OS

[jcarranzan]

Summary

Currently there are some failures in our win jobs related to QuarkusCliConfigEncryptIT because special characters Strings in QuarkusCliConfigEncryptIT class on Windows OS

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

[github-actions]

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

[michalvavrik]

rsvoboda requested a review from michalvavrik 7 minutes ago

this fix is needed, @jcarranzan is testing it ATM, there are other places that could be escaped as well

quarkus-test-framework/quarkus-test-cli/src/main/java/io/quarkus/test/bootstrap/config/QuarkusSetConfigCommandBuilder.java

Line 62 in 1eac846

subCommand.add(propertyValue);

but it is not required to fix tests itself

[jcarranzan]

I did a partial fix and additional improvements needs to be done to be working on Windows OS because still there are other issues:

[ERROR] Errors: 
[ERROR]   EncryptPropertyTest.encryptSecret_PlainKeyFormat_ExistingEncryptionKey:44->getSecret2:84 ? Runtime java.lang.IllegalArgumentException: Illegal bas
e64 character 5b
[ERROR]   EncryptPropertyTest.encryptedSecret_Base64SecretFormat_GeneratedEncryptionKey:39->getSecret1:80 ? Runtime java.lang.IllegalArgumentException: Ille
gal base64 character 5b
[ERROR]   EncryptPropertyTest.failToDecryptSecretInWrongFormat:60->getSecret3:88 ? Runtime java.lang.IllegalArgumentException: Illegal base64 character 5b  
[INFO]
[ERROR] Tests run: 6, Failures: 0, Errors: 3, Skipped: 1

[michalvavrik]

Remaining failure for the set config test I cannot fix after spending days on that. I think when it's consequence of default encoding. We cannot expect that it will work without adjusting of the defaults on executors.