test_runner: pass abort signal to test

[MoLow]

this PR introduces both passing an abort signal to a test

test('promise abort signal', { signal: AbortSignal.timeout(1) }, async (t) => {
  // ...
});

and reciving an abort signal inside a test

test('subtest', async (t) => {
  await fetch('', { signal: t.signal });
});

todo:

• wait for test_runner: support timeout for tests #43505 to land, this is rebased on top of it
• docs
• tests

[cjihrig]

I'm not opposed to supporting abort signals here if other people want it, but numeric timeouts should absolutely be supported too.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/44863/

[MoLow]

CC @benjamingr @cjihrig @ljharb

[ljharb]

I think it's a huge mistake to integrate more things with AbortSignal - the only cancellation mechanism anything should support is whatever TC39 ends up going with.

[benjamingr]

I think it's a huge mistake to integrate more things with AbortSignal - the only cancellation mechanism anything should support is whatever TC39 ends up going with.

AbortSignal is Node's and the web's cancellation primitive and it's what we're going with. This is doubly so since Chrome are blocking any cancellation primitive at TC39 due to their belief that AbortSignal is the web's cancellation primitive.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/45438/

[ljharb]

@benjamingr and the more environments integrate AbortSignal with more things, the less likely it is that Chrome's block will be overcome.

[aduh95]

/cc @nodejs/test_runner

[targos]

The commit lands cleanly on v16.x but message tests fail so this needs a backport.
Feel free to add #43919, #43911, #43843, and #43887 to the backport PR as they are blocked by this one.

[MoLow]

@targos this was adjusted in https://github.com/nodejs/node-core-test
see nodejs/node-core-test#28 (comment)
anything I can do to help backporting these 4 PR's?

[targos]

@MoLow There's a guide in https://github.com/nodejs/node/blob/main/doc/contributing/backporting-to-release-lines.md#how-to-submit-a-backport-pull-request

But nodejs/node-core-test#28 (comment) was enough to help, thank you! I cherry-picked 3f72c72 and it fixed everything.