Introduce server.abort(request: Request) to abort an in-flight HTTP/HTTPS request

[Jarred-Sumner]

What does this PR do?

Introduce server.abort(request: Request) to abort an in-flight HTTP/HTTPS request.

This immediately closes the TCP socket.

One subtlety here is we have to make sure that we don't call drain microtasks directly in the abort handler. Instead, we have to go through the event loop enter/exit - so that we don't drain microtasks inside of the .abort() function call itself.

How did you verify your code works?

There are tests

[robobun]

^{Updated 1:12 AM PT - Jan 28th, 2025}

❌ @Jarred-Sumner, your commit ee239d7 has 1 failures in Build #10691:

• test/cli/install/bun-install-registry.test.ts - 1 failing on 🪟 2019 x64
• test/cli/install/bun-install-registry.test.ts - 3 failing on 🪟 2019 x64-baseline

---

🧪   try this PR locally:

bunx bun-pr 16830

[cirospaciari]

this.flags.user_called_abort should be part of isAbortedOrEnded otherwise will be a footgun in future.

Also after calling abort the request_context should be detached from AnyRequestContext to avoid accessing invalid data

I would also duplicate all tests for TLS and non-TLS

[cirospaciari]

Suggested change

	rejectUnauthorized: false,
	ca: tls.cert,

[Jarred-Sumner]

this.flags.user_called_abort should be part of isAbortedOrEnded otherwise will be a footgun in future.

Also after calling abort the request_context should be detached from AnyRequestContext to avoid accessing invalid data

us_socket_close callback calls the onAbort callback, which triggers the normal request abort flow. I think it's less likely to cause bugs if we can rely on the same code paths continuing to be used without changes