Add DOMException

[bptato]

Implemented separately from the other errors because it is defined in terms of WebIDL, where members of an interface are getters on their prototype.

See the difference between
JSON.stringify(Object.getOwnPropertyDescriptors(new TypeError())) vs JSON.stringify(Object.getOwnPropertyDescriptors(new DOMException())).

(Required for btoa/atob and structuredClone; ref. #16, #1032)

[bptato]

Note: this was complaining because of the bytecode version, but I don't know how the corpus was generated so I just incremented it manually...

[bptato]

It's still missing a stack trace when created with the constructor...

[bptato]

I was confused for a minute because browsers set stack as a getter on error prototypes, but we set it as a property on individual Error objects. I ended up following our existing practice.
(stack itself is non-standard; the spec only says that if regular Errors have it, DOMException should also have it.
I don't know if the difference matters anywhere in practice.)

[saghul]

Perhaps you could use Js_NewError and extract it?

[saghul]

I was confused for a minute because browsers set stack as a getter on error prototypes, but we set it as a property on individual Error objects. I ended up following our existing practice.

(stack itself is non-standard; the spec only says that if regular Errors have it, DOMException should also have it.

I don't know if the difference matters anywhere in practice.)

I think that should be fine.