Enhance McpClientAuthProvider that uses client_credentials to support named OIDC clients #2090
Description
Currently, no matter how many secured MCP servers are used, McpClientAuthProvider that uses client_credentials works with a global/default OIDC client configuration.
Quarkus OIDC client may have multiple named configurations and McpClientAuthProvider can be bound to named MCP client configurations...
And we need to make sure that McpClientAuthProvider that uses client_credentials can be bound to a named OIDC client credentials, so that MCP servers with totally unrelated OIDC connection details can be supported.
CC @cescoffier