Fix #25719: ruby-nextgen parses JSON response bodies twice
Fixes #25719
Configuration#configure_faraday registered Faraday's :json response middleware (decoding bodies once), and Connection#deserialize then re-ran JSON.parse on any body still a String. A JSON response whose value is a string ("hello") was decoded by the middleware to the bare string, and the second parse failed → ApiError on a successful call (reproduced verbatim on upstream master).
The response middleware is removed — Connection#deserialize is the single parse point (request-side :json untouched). Generator test + fixture assert the generated configuration.rb has no conn.response :json while connection.rb keeps JSON.parse; both generated runtimes regenerated (one-line diff each). New runtime regression spec covers the issue's scenario: JSON string body → "hello", model building, invalid JSON → ApiError, empty body → nil.
Sample rspec 27/27; RubyNextgenClientCodegenTest 25/25; RubyApiRoutingTest 6/6.
Summary by cubic
Fixes the ruby-nextgen client raising ApiError on successful JSON responses whose value is a string, such as "hello", because the response body was parsed twice.
Bug Fixes
- Removes Faraday's
:jsonresponse middleware so JSON parsing happens only inConnection#deserialize. - Adds generator and runtime specs covering JSON string, model, invalid JSON, and empty response bodies.
- Regenerates Ruby samples (
qdrant,petstore) with the updated configuration.