next.js

75718952 - Handle cancellation errors during response clone cleanup (#100961)

Handle cancellation errors during response clone cleanup (#100961) ## Summary A response body can fail after `fetch()` resolves, for example when an upstream connection closes. Even if the caller catches the body-read error, garbage-collection cleanup of an unused response clone can call `cancel()` on its already-errored stream. That cancellation rejects, and the existing `.then(noop)` leaves the rejection unhandled. Depending on the runtime’s unhandled-rejection handling, this can terminate the process. Use `.catch(noop)` to handle cancellation failures during cleanup. The original body-read error still reaches the caller. Related: https://github.com/vrv/vercel-runtime-cache-cancel-repro