Fix Error clone() when structuredClone uses bad prototype

[kanongil]

Originally reported in #398 (comment).

This can happen in jest which uses node vm to isolate runs.

[kanongil]

Note that this could actually be a node.js error.

It seems incorrect that a created Error, and the Error used for structured clones use different prototypes within the same VM runtime.

[Marsup]

For the record, I rebased the next branch and had to alter your original commits, it should preserve the behavior while getting rid of the structuredClone check.

[kanongil]

FYI this is just a jest issue.

It is 100% responsible for exposing structuredClone() in the VM and returning errors with the correct prototype, as the VM doesn't expose anything by itself.