[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

まず、PHP クライアントの initialize ネゴシエーションと、resource_metadata が存在しない場合の WWW-Authenticate の処理を追跡します。revision 2025-03-26 を条件として、MCP origin と issuer から導出される URL に対する順序付きの Discovery 分岐を実装し、テストします。blocker #317 と #318 の解決後に、ユニットテストの分岐と auth/2025-03-26-oauth-metadata-backcompat および auth/2025-03-26-oauth-endpoint-fallback の conformance シナリオを確認します。