Integrate with Looker MCP server And Yahoo OS Design MCP server

[yosrixp]

Summary

Integrate two MCP servers: Looker (7 instances) and Yahoo OS Design.

Looker MCP

• OAuth/OIDC for the 7 Looker instances (maw, ouryahoo, finance, hr, search, enterprise, prism-mail), each modeled as its own provider id / Quarkus OIDC tenant with a per-instance /<provider>/authorize/callback redirect URI.
• Public PKCE (token_endpoint_auth_method=none, S256), ~1h access token, non-rotating refresh token (refresh_token:null on refresh) preserved via LookerUpstreamRefreshClient; all instances L2-promoted for cross-window AT amortization.
• One shared, parameterized TokenExchangeServiceLookerImpl + LookerUpstreamRefreshClient (provider label per instance) to avoid 7x duplication.
• Open-source application.yaml uses ${LOOKER_*_HOST/RESOURCE/CLIENT_ID} placeholders (no internal hostnames); real hosts/client_ids injected per env via configmap + dev/stage/prod values.
• prism-mail wired ahead; its upstream OAuth app is pending enablement.

Yahoo OS Design MCP

• Wire up the yahoo-os provider deploy config: resource-mapping (/v1/yahoo-os-design/mcp, audience yahoo-os) across dev/stage/prod. (Token-exchange impl TokenExchangeServiceYahooOsImpl landed in a prior submodule commit.)

Changes

• New (Looker): LookerResource, LookerUpstreamRefreshClient, TokenExchangeServiceLookerImpl, LookerInstances, LookerConfig; registered in TokenExchangeServiceProducer, UpstreamProviderClassifier, OauthProviderLabel.
• Config: OIDC tenants, resource-mapping, upstream-token TTLs, remote-servers endpoints for Looker (+ yahoo-os resource-mapping) in application.yaml / application.dev.yaml / Helm configmap.yaml + stage/prod values.

Test plan

• Unit tests pass (Looker*, YahooOs*, producer, classifier) — 226 run, 0 failures.
• Local dev OAuth round-trip for looker-ouryahoo (gateway → MoP → Looker → token + userinfo).
• Stage e2e via gateway for Looker and yahoo-os once redirect URIs are registered.