Bound OAuth response bodies in the client

## Motivation and Context

`MCP::Client::HTTP` caps a single message from the server at 4 MiB, but the OAuth flow talks to
authorization endpoints over its own Faraday connection, and that one had no cap. Discovery,
dynamic client registration, and token responses were buffered in full and handed to `JSON.parse`,
so a server that answered an OAuth request with an endless body grew the client's memory for as
long as it kept sending.

`Flow` and `IDJAGTokenExchange` each build their own connection, so both needed the bound.
The new `BoundedBody` counts bytes in a Faraday `on_data` callback and refuses the response once
it passes `MAX_RESPONSE_BYTES`, which matches the 4 MiB of `MCP::Client::HTTP::MAX_MESSAGE_BYTES`
and `MCP::Client::Stdio::MAX_LINE_BYTES`. It hands back the status paired with the bounded body
rather than the Faraday response, so no later caller can reach the unbounded `response.body`.

Those bytes are counted after decompression. The default Net::HTTP adapter negotiates `Accept-Encoding`
itself  and reads the body through `Net::HTTPResponse#inflater`, so a small compressed body that expands past
the cap is refused partway through the expansion. That holds only while the connection leaves
`Accept-Encoding` alone, which is now recorded in a comment on both `default_http_client` definitions.

An over-cap response is refused rather than truncated: a partial discovery or token document cannot be validated.
Protected resource metadata is the one place where refusing is not fatal, since any PRM discovery failure
already selects the legacy authorization path by design.

## How Has This Been Tested?

New unit tests in `test/mcp/client/oauth/bounded_body_test.rb` cover the streaming path,
the at-limit boundary, and the fallback for adapters that ignore `on_data`. One of them serves
a gzip body over a real socket rather than through WebMock, which returns a stubbed body verbatim
and never runs the inflater; it fails if the cap ever starts measuring compressed bytes. New tests in
`test/mcp/client/oauth/flow_test.rb` and `test/mcp/client/oauth/id_jag_token_exchange_test.rb` drive each of
the four request wrappers end to end with an over-cap body; all five fail without the cap in place.

## Breaking Changes

An OAuth endpoint response larger than 4 MiB is now rejected instead of parsed.

test/mcp/client/oauth/flow_test.rb

@@ -948,6 +948,69 @@ module MCP
           assert_match(/authorization_servers/i, error.message)
         end
 
+        def test_run_refuses_an_authorization_server_metadata_body_over_the_cap
+          stub_request(:get, @as_metadata_url).to_return(
+            status: 200,
+            headers: { "Content-Type" => "application/json" },
+            body: over_cap_body,
+          )
+
+          error = assert_raises(Flow::AuthorizationError) { run_authorization_flow }
+
+          assert_match(/exceeds \d+ bytes/, error.message)
+        end
+
+        def test_run_refuses_a_protected_resource_metadata_body_over_the_cap
+          # PRM discovery failures select the legacy path by design, so the refusal shows up as
+          # the fallback rather than as a raise. The padded document is valid JSON naming
+          # an authorization server, so contacting that server is exactly what would happen
+          # if the body had been read: the assertion below fails if the cap stops working.
+          stub_request(:any, %r{\Ahttps://srv\.example\.com/}).to_return(status: 404)
+          stub_request(:get, @prm_url).to_return(
+            status: 200,
+            headers: { "Content-Type" => "application/json" },
+            body: JSON.generate(
+              resource: "https://srv.example.com/mcp",
+              authorization_servers: [@auth_base],
+              padding: "a" * (4 * 1024 * 1024),
+            ),
+          )
+
+          assert_raises(Flow::AuthorizationError) { run_authorization_flow }
+
+          assert_not_requested(:get, @as_metadata_url)
+        end
+
+        def test_run_refuses_a_dynamic_client_registration_body_over_the_cap
+          stub_request(:post, "#{@auth_base}/register").to_return(
+            status: 201,
+            headers: { "Content-Type" => "application/json" },
+            body: over_cap_body,
+          )
+
+          error = assert_raises(Flow::AuthorizationError) { run_authorization_flow }
+
+          assert_match(/exceeds \d+ bytes/, error.message)
+        end
+
+        def test_run_refuses_a_token_endpoint_body_over_the_cap
+          stub_request(:post, "#{@auth_base}/token").to_return(
+            status: 200,
+            headers: { "Content-Type" => "application/json" },
+            body: over_cap_body,
+          )
+
+          error = assert_raises(Flow::AuthorizationError) { run_authorization_flow }
+
+          assert_match(/exceeds \d+ bytes/, error.message)
+        end
+
+        # One byte past the cap, so the three request wrappers are each proven to install the streaming callback.
+        # A wrapper that forgot it would buffer this whole body and parse it.
+        def over_cap_body
+          "a" * (4 * 1024 * 1024 + 1)
+        end
+
         def test_run_raises_when_token_response_is_not_a_json_object
           # The token endpoint MUST return a JSON object per RFC 6749 §5.1.
           # A non-object body would otherwise be persisted into the provider