Minor OIDC updates

[sberyozkin]

I've noticed Guillaume started preparing for 3.17.4, so here is a PR with 2 minor OIDC updates, following some recent demo experiments:

• When quarkus-oidc fails to exchange the code for tokens, it will pass the authorization endpoint URI, as opposed to the correct token endpoint URI to the method which logs this URI in case of the error, I've been confused by it for a while, since it is only a user who is facing the authorization endpoint challenge, quarkus-oidc never calls it directly, it only calls the token endpoint
• OIDC Client registration URI, even though it may have been discovered by quarkus-oidc, is not visible to the code which has OidcConfigurationMetadata injected. It is not a big problem, https://quarkus.io/guides/security-openid-connect-client-registration does not require it, and it is expected that quarkus-oidc-client-registration can function completely independently, without even expecting quarkus-oidc loaded. But quarkus-oidc-client-registration needs the registration URI to initialize itself, so if quarkus-oidc is loaded, it may as well pick up the already discovered registration URI

[github-actions]

🎊 PR Preview 47567e7 has been successfully built and deployed to https://quarkus-pr-main-44986-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.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 298daf3.

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

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