Propagate Quarkus properties for Gradle Test tasks

[radcortez]

Quarkus configuration from Gradle does not propagate for Test tasks. Usually, our Quarkus tasks do that automatically, but in this case, we are using the Gradle Test task, which doesn't use our own.

• Fixes AOT Cache is not being generated #53059

Update:

SystemPropsAsBuildTimeConfigSourceTest was failing because it was setting a quarkus config as a system property (not propagated), and checking that an Env Var with the same name was the value being used. With this change, it uses the default Config ordinality for sources (System before Env).

The test was added in #37021, which also fixed issues with config propagation in Gradle. I don't see a reason why the test checks for the non-propagation of system properties in this case. Maybe we need @aloubyansky to check this as well.

[radcortez]

Updated the description with some more information.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 1833a6e.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.