fix(node/http): set res.complete before emitting end event

[ddmoney420]

Summary

Fixes the timing of when res.complete is set to true on IncomingMessage to match Node.js behavior.

Fixes #26733

Problem

When using node:http for HTTP requests, the res.complete property was false inside the end event handler, even though the request completed successfully. This broke packages like @adyen/api-library which check:

res.on("end", () => {
    if (!res.complete) {
        reject(new Error("The connection was terminated while the message was still being sent"));
    }
});

Root Cause

1. complete was only being set to true in _destroy, which happens AFTER the end event
2. In Node.js, complete is set in parserOnMessageComplete BEFORE push(null) triggers end
3. There was also a logic bug where complete = true was set before the !this.complete check

Solution

1. Set this.complete = true in _read() BEFORE calling this.push(null)
2. Fixed logic in _destroy() to check !this.complete before setting it to true

Test plan

• Added regression test that verifies complete is true in end event
• Verify @adyen/api-library works correctly

🤖 Generated with Claude Code

[CLAassistant]

All committers have signed the CLA.