fix: add name property to exported interface errors

[2color]

Description

As discussed in ipfs/helia-verified-fetch#25 (comment), this PR adds the name property to the AbortError type.

This has a couple of benefits:

• Sticks the common convention for Error types (all built in Error types have the name property set to the class name)
• Allows checking the error type at runtime in a TS codebase without importing the type

Notes & open questions

• Should we also set the name property on UnexpectedPeerError, InvalidCryptoExchangeError and InvalidCryptoTransmissionError?

Change checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if necessary (this includes comments as well)
• I have added tests that prove my fix is effective or that my feature works

[SgtPooki]

nodejs/node#40692 (comment) has some relevant discussions about custom AbortError's too. Also some deets in ipfs/helia-verified-fetch#25 (comment)

[achingbrain]

The fetch spec says things like:

Let fallbackError be an "AbortError" DOMException.

...so I think longer term, in order to be closer to the spec, this class should be changed to extend DOMException instead of Error, then we get the .name property for free.

DOMException was added to Node.js in v17 so we are good to use it.

Unfortunately .code on DOMException is a number and not a string so it may be a breaking change, I'm not sure if we can override that for compatibilities sake, it may need testing out locally first.

[achingbrain]

Should we also set the name property on UnexpectedPeerError, InvalidCryptoExchangeError and InvalidCryptoTransmissionError?

Sorry, missed this - yes, I think we should.

[2color]

Should we also set the name property on UnexpectedPeerError, InvalidCryptoExchangeError and InvalidCryptoTransmissionError?

Sorry, missed this - yes, I think we should.

Ok I'll update the pr

[achingbrain]

Just noticed that DOMException officially doesn't have a .stack property, and technically neither does Error, though every JS runtime adds it - there's a tc39 proposal to add it that's been around for, oh, 8 years 🤦