Update OIDC client filters to check if OIDC client feature is enabled

[sberyozkin]

Fixes #41827.

When the OIDC client filter is registered with the @OidcClient annotation, disabling the OIDC client feature with quarkus.oidc-client.enabled=false makes @OidcClient ineffective because it is processed at the OIDC client filter build time and is preconditioned on the underlying OIDC client feature being enabled.

However, when the OIDC client filter is registered directly using a @RegisterRestClient annotation, the fact that the OIDC client feature is disabled with quarkus.oidc-client.enabled=false is not relevant, it is just a standard, generic JAX-RS provider registration. Then, when the request is made, the filter tries to do something with the disabled client and the request fails.

This PR attempts to fix it by updating OIDC client filters to check the build time quarkus.oidc-client.enabled property and avoid any OidcClient related initialization or processing if it is disabled.

The test has been updated. Specifically, when the OIDC client is disabled, the test gets 401 when a secured ProtectedResource method is called because it does not get an expected token. But it gets an empty response when a public method in the ProtectedResource is called, proving no token is arriving, with the OidcClient filter not impacting the request flow, even though the OidcClient is disabled.

When the OidcClient is enabled, the public method returns a user name, similarly to when a secured method is called, due to the proactive authentication, proving the token is flowing in this case as well

[github-actions]

🎊 PR Preview 14af184 has been successfully built and deployed to https://quarkus-pr-main-43374-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[michalvavrik]

Changes LGTM.

[sberyozkin]

@michalvavrik I've tried to make related log messages more informative as you suggested, have a look please

[michalvavrik]

In my eyes that's better, thank you

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 6092c24.

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

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 6092c24.

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