Integrate Rootly, YSynapse, and UDS MCP servers + fix Maven wrapper on clean CI checkout

[yosrixp]

Summary

Adds three new MCP provider integrations to the OAuth proxy (MoP) and fixes a
CI build break caused by the Maven wrapper jar not being tracked. The product
code lands via a mcp-oauth-proxy submodule bump; the parent repo wires the new
providers into the dev MCP gateway across stage and both prod regions.

Changes

New MCP provider integrations (submodule)

• Rootly — new RootlyResource, TokenExchangeServiceRootlyImpl, and
  RootlyUpstreamRefreshClient, registered in TokenExchangeServiceProducer,
  UpstreamProviderClassifier, K8SSecretsProvider, and OauthProviderLabel,
  with full unit-test coverage and Helm configmap.yaml / values.yaml wiring.
• YSynapse — new TokenExchangeServiceYahooSynapseImpl with yahoo-synapse
  audience constant, exchange-step/provider-label telemetry, and tests. mTLS
  disabled for this provider.
• UDS — new TokenExchangeServiceUdsImpl with uds audience constant,
  telemetry wiring, and tests.

Deployment / gateway config (parent repo)

• Registered yahoo-synapse and uds MCP gateway routes (/v1/yahoo-synapse/mcp,
  /v1/uds/mcp) in stage and both prod regions.
• Expanded Datadog read scopes and dropped mcp_write.
• L2 refresh-token TTL entry added for rootly (6 months).
• CI workflow / settings updates (.github/workflows/ci.yml, ci-settings.xml,
  helm-deploy-reusable.yml).

Build / CI fix

• Track .mvn/wrapper/maven-wrapper.jar so ./mvnw works on a clean CI
  checkout (previously git-ignored, which broke fresh-checkout builds).