Improve OIDC client reference document

[sberyozkin]

The OIDC client reference document has some problems at the moment:

• It does not have the generated OIDC client properties
• Examples where OidcClient is used directly are pretty bad, they were added awhile back, the assumption was the users who chose to use OidcClient directly would write some code manually acquiring and refreshing tokens, but it is not good for new users

So this PR does the following:

• Adds a Configuration section where OIDC client properties are listed. Also I've added another section there showing the token propagation properties (the PR refers to the old quarkus-oidc-token-propagation-reactive because the directory has not been changed - but the generated properties correctly show the quarkus.rest-client-oidc-token-propagation namespace)
• Improve several sections showing how to use OidcClient directly, without relying on the filter
• It also fixes a typo where a tenant-id attribute is mentioned

@rolfedh Can you please do a Doc team check on this PR, mostly, these are code examples, but there is a bit if extra text there as well

[github-actions]

🙈 The PR is closed and the preview is expired.

[sberyozkin]

@sheilamjones I've noticed Rolfe is away, would you be OK with doing a review. The actual text changes are quite limited, but I'm asking the Doc team to check given that it will be eventually synced to the downstream docs. May be I can just merge as the team will likely be doing the whole doc review later anyway.

[sheilamjones]

Hi @sberyozkin, sure, I will take a look now.

[sheilamjones]

Hi @sberyozkin, I completed a review focusing on your changes only. I just had some minor comments for your consideration and also a couple of questions. Hope this helps.
Kind regards,
Sheila

[sberyozkin]

Hi @sheilamjones Thanks very much for the prompt review, applied all proposed changes, and I'll also do a minor clarification re the header and the scheme, thanks

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 68229c0.

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

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

You can consult the Develocity build scans.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 68229c0.

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

[sberyozkin]

Let me merge it now, so that I can link to the doc snapshots showing the generated properties, thanks @sheilamjones @gastaldi.

Sheila, FYI, I only did a minor update after applying your suggestions, with You can use 'OidcClient' directly to acquire access tokens and set them in an HTTP Authorizationheader as aBearer scheme value. without focusing on the actual technical representation like I did with Authorization: Bearer - since the user would not have to set : etc...

Thanks

[sberyozkin]

These changes should be backportable I hope

[sberyozkin]

Sorry, @sheilamjones, if you think I merged too early, let me know, I'll apply other suggestions you may have right away :-)

[rolfedh]

LGTM