fix(node:http) resume when reading and avoid unnecessary pause/resumes calls

[cirospaciari]

What does this PR do?

Fix: #18799

• Documentation or TypeScript types (it's okay to leave the rest blank in this case)
• Code changes

How did you verify your code works?

Tests

[robobun]

^{Updated 4:08 PM PT - Apr 7th, 2025}

❌ @cirospaciari, your commit 1270f4b has 1 failures in Build #14600:

• test/js/web/fetch/fetch.test.ts - 1 failing on 🍎 14 aarch64

---

🧪   try this PR locally:

bunx bun-pr 18804

[Jarred-Sumner]

Whether or not it's paused probably needs to go on the NodeHTTPSocket instead of the NodeHTTPResponse, right? Since the socket can outlive the response and we don't want to end up in a state where the previous response was paused and then the next request never happens

[cirospaciari]

Whether or not it's paused probably needs to go on the NodeHTTPSocket instead of the NodeHTTPResponse, right? Since the socket can outlive the response and we don't want to end up in a state where the previous response was paused and then the next request never happens

The socket will always be resumed if outlived, is_paused is needed here because it direct uses usockets with do not track this state raw_response is a opaque struct, we can change this flag to be inside usockets with makes more sense