Remove use of Json in OIDC

[geoand]

• Relates to: Jakarta JSON-P Json.*** methods are crazily inefficient #42748

[github-actions]

🎊 PR Preview 4865eae has been successfully built and deployed to https://quarkus-pr-main-44339-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 b7e58d6.

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

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

[sberyozkin]

Thanks @geoand, I did not realize it was slow on the builder path as well, happy to see it all replaced with the optimized reference.
FYI, the reason it is used on some OIDC public API paths is because it is also available at the JsonWebToken API level as a possible claim value, so I tried to keep it consistent...

Thanks

[geoand]

@sberyozkin you were absolutely right to use Json - that's what we were all doing until @gsmet found how horribly slow it is.