Pass the client and tenant id to OIDC request filters

[sberyozkin]

Fixes #39320

If the application has multiple OIDC client or OIDC server configurations then distinguishing between them in custom OIDC request filters using the request URI only can be difficult.
So the client-id is passed when the filters are applied to quarkus-oidc-client requests and the tenant-id when the filters are applied to quarkus-oidc requests, Having differently named attributes will help if the quarkus-oidc-client is used in the endpoints secured with quarkus-oidc, in which case the filter will be called by both server-side and client-side OIDC extensions - though we may also add a Scope annotation (Scope.SERVER, Scope.CLIENT) later to help in such advanced cases

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 96e162c.

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