Cloned responses do not clone the underlying stream

[cprecioso]

Describe the bug
Doing a fetch, and then cloning the Response will give you 2 response objects.
In the browser, you can use these separately, and when you consume the Response, the other one is not consumed (as described on MDN).
In happy-dom, consuming either of them will consume both, rendering the .clone() operation useless.

To Reproduce

// test.mjs
import { Window } from "happy-dom";

const window = new Window();

const originalResponse = await window.fetch(
  "https://pokeapi.co/api/v2/pokemon/ditto"
);
const clonedResponse = originalResponse.clone();

console.log("ORIGINAL", await originalResponse.text()); // Will show the response
console.log("CLONED", await clonedResponse.text()); // Will return an empty string

• If you change the order of the two last lines, whichever comes first will work and the second one will not.
• Responses created from Response.json({foo:"bar"}) do not have this bug
• If you immediately repeat the fetch(), both requests will work correctly (I suspect this is due to correctly implemented cloning for the internal cache).

Expected behavior
Both response objects return the correct response text even if the other one has been consumed.
You can copy the code (minus the new Window()) to your browser console and see it working correctly.

Screenshots
-

Device:
node v20.11.0 on macOS Sonoma 14.2.1

Additional context
-