Show how to handle multiple OIDC token audiences

[sberyozkin]

Related to #40658

This PR updates a few OIDC wiremock tests to confirm that when code flow ID and access tokens have different audiences, then 2 options are available:

• Set expected audience to any (with the expected follow up to use a custom Jose4JValidator - the test only checks that audience=any does not cause a failure and confirms that ID and access tokens do have different audiences)
• Set expected audience to a list of all allowed audiences

[quarkus-bot]

Status for workflow Quarkus CI

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

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