Rewrite the internal Web Stream native bindings to use less memory

[Jarred-Sumner]

What does this PR do?

Fixes #12198
Closes #16075

The usage of type: "bytes" in our lazy internal ReadableStream sources led to a memory leak because each read from the stream sometimes returns a larger & different buffer than the one the user provides.

How did you verify your code works?

The version using Node APIs uses the same amount of memory as the version using Bun/Web APIs.

Will follow up with a memory leak test once a release build is generated in CI.

[robobun]

^{Updated 12:47 AM PT - Jan 26th, 2025}

❌ @Jarred-Sumner, your commit 2827f0b has 5 failures in #10577:

• test/js/web/fetch/fetch.stream.test.ts - 5 failing on 🍎 14 x64
• test/js/web/fetch/fetch.stream.test.ts - 5 failing on 🍎 13 x64
• test/js/node/tls/node-tls-connect.test.ts - 1 failing on 🐧 12 aarch64
• test/js/web/fetch/fetch.test.ts - 1 failing on 🍎 13 aarch64
• test/js/node/test/parallel/test-http-chunk-problem.js - code 1 on 🍎 13 aarch64
• test/js/node/test/parallel/test-http-chunk-problem.js - code 1 on 🍎 14 aarch64
• test/cli/install/bun-install-registry.test.ts - 1 failing on 🪟 2019 x64

---

🧪   try this PR locally:

bunx bun-pr 16349

[leeoniya]

totally drive-by comment, but a PR title like "Streams: Fix memory leak with type: "bytes"" would be much nicer than "Fixes #12198". does the tl;dr without clicking around for context :)

[DonIsaac]

Additionally, JSC's GC was not being informed of allocations in BufferedReader. Since the GC didn't know memory pressure was increasing, it never knew it needed to sweep old objects out of the heap. This is now fixed.