Add support for aborting a request using AbortSignal

[segevfiner]

This adds support for passing an AbortSignal. Adding support for ClientRequest.destroy & ClientRequest.setTimeout will require figuring out an appropriate change to the inject interface as it currently doesn't return such a pending request object but only has a callback or promise. Also note that such cancellation and timeouts should effect technically also effect the socket causing it to emit appropriate events and/or change state. But we aren't emulating much of the socket ATM.

Relates to #203

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[mcollina]

lgtm

[mcollina]

@Fdawgs it seems CI is not running, could u take a look?

[Fdawgs]

@Fdawgs it seems CI is not running, could u take a look?

I have no idea why @mcollina, this PR should have triggered it. 😕

Have tested the CI with both a direct PR in this repo (#206) and from a fork (#207) and they both triggered.

[segevfiner]

Let me push a no-op amend and see if it triggers. Maybe GitHub glitched.

[Fdawgs]

There we go, thanks @segevfiner!

[segevfiner]

Derp. AbortController is not available on Node 14.x... I wonder how do we want to handle that...

[mcollina]

Maybe throw if those things are not available?

You can use { skip: !global.AbortController } to skipt the test.

[mcollina]

You'll need to ignore those lines from the code coverage.

[mcollina]

this now conflicts with master

[mcollina]

lgtm