Avoid mixing @ConfigMapping and legacy @ConfigRoot in OIDC token propagation

[gsmet]

This is going to be a problem with the new extension annotation processor.

@michalvavrik could you have a look? I find it odd we are mixing the two approaches, especially since you are very thorough. Did you have a reason to keep the old @ConfigRoot pattern for the build time config? Maybe there was a limitation that got lifted? I ran the module tests and the module ITs and it was going fine.

@radcortez for sanity check

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 160e95b.

✅ 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.

[michalvavrik]

I checked the file history and can't find a good reason why I didn't make this a @ConfigMapping. I think I made mistake. Changes LGTM. Thanks

[gsmet]

Yeah it's easy to miss them or to just move to the new format when creating new config.

From now on, we will need consistency inside a given module thus why the fix.

Thanks for the confirmation!