[Client] Add OAuth 2025-03-26 metadata backcompat fallback

Context

Older MCP servers (spec revision 2025-03-26) do not publish /.well-known/oauth-protected-resource. The client must fall back to discovering OAuth metadata directly from the MCP server origin's /.well-known/oauth-authorization-server and, if missing, from the issuer derived by URL convention.

Scope

• Order of operations when WWW-Authenticate lacks resource_metadata:
  1. Try /.well-known/oauth-protected-resource at MCP server origin.
  2. Try /.well-known/oauth-authorization-server at MCP server origin.
  3. Fall back to OIDC discovery (/.well-known/openid-configuration).
• Track protocol revision negotiated during initialize; only enable fallback chain when the server announced 2025-03-26.

Conformance scenarios unblocked

auth/2025-03-26-oauth-metadata-backcompat, auth/2025-03-26-oauth-endpoint-fallback.

Dependencies

Blocked by: #317, #318.

Acceptance

• Unit tests covering all fallback branches.
• Conformance: 2 baseline scenarios pass.

cc @soyuka

Inizia tracciando la negoziazione di initialize del client PHP e la gestione di WWW-Authenticate quando resource_metadata è assente. Implementa e testa i rami ordinati di Discovery per l’origine MCP e l’URL derivato dall’issuer, subordinati a revision 2025-03-26. Verifica i rami dei test unitari e gli scenari di conformità auth/2025-03-26-oauth-metadata-backcompat e auth/2025-03-26-oauth-endpoint-fallback dopo che i blocker #317 e #318 saranno stati risolti.