fix: resolve request hang with large API responses

[angeloashmore]

Resolves: #435

Description

Fixes requests hanging indefinitely in Node.js 22+ when using methods like getByType(), get(), etc.

Root cause: The request() function deduplicates concurrent GET requests to the same URL, sharing a single Response across callers. It then called response.clone() so each caller could read the body independently. In Node.js 22+, cloned responses share the same underlying stream — if the original response body is never consumed, backpressure blocks the clone from being read, causing .json() to hang forever.

Solution: Instead of cloning, buffer the response body as a blob immediately when the response is received, then derive text/JSON from the buffered blob on demand. This eliminates response.clone() entirely and works for both text (JSON API responses) and binary data (image uploads via WriteClient).

Checklist

• If my changes require tests, I added them.
• If my changes affect backward compatibility, it has been discussed.
• If my changes require an update to the CONTRIBUTING.md guide, I updated it.

How to QA

1. Run existing tests: npm test
2. Test with Node.js 22+:

   const client = prismic.createClient("your-repo")
   const results = await client.getByType("your-type", { pageSize: 100 })
   // Should complete without hanging

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[TUNER88]

LGTM 👍