Drop unnecessary captureStackTrace call

[fregante]

I'm not sure I understand this call. NonError extends Error, which already captures the stack natively:

❯ node
Welcome to Node.js v16.4.2.
Type ".help" for more information.

> new class NonError extends Error {name='NonError'}
NonError
    at REPL1:1:1
    at Script.runInThisContext (node:vm:129:12)
    at REPLServer.defaultEval (node:repl:522:29)
    at bound (node:domain:416:15)
    at REPLServer.runBound [as eval] (node:domain:427:12)
    at REPLServer.onLine (node:repl:849:10)
    at REPLServer.emit (node:events:406:35)
    at REPLServer.emit (node:domain:470:12)
    at REPLServer.Interface._onLine (node:readline:487:10)
    at REPLServer.Interface._line (node:readline:852:8)

[sindresorhus]

It used to be required to get a stack trace for error subclasses, but I think JS engines fixed that at some point.

[fregante]

Oh I suppose that was the case when Error was not subclassable. I did see some weird stuff to support that.

[sindresorhus]

The subclassing syntax worked initially, but it didn't actually properly subclass or something since Error was a built-in.