Background errors not serialized correctly when sent to UI

[Gudahtt]

Describe the bug
When an error occurs in the background, it's not serialized correctly when sent to the UI. The error arrives as a plain object with its stack missing, so the resulting Sentry reports are difficult to debug.

Expected behavior
The error should still have a type of Error and should retain its stack when sent from the background to the UI.

[Gudahtt]

The error is being serialized like this by dnode. @rekmarks investigated this and might have a solution but it'd involve forking dnode and various other libraries that it depends upon, and we're not especially eager to maintain a fork of all of that stuff.

We could also consider replacing dnode with an alternative, like capnode or capTP. Or we could drop this abstraction entirely and use JSON-RPC directly.

[sentry]

Sentry issue: METAMASK-GP0Z

[sentry]

Sentry issue: METAMASK-GN3N

[sentry]

Sentry issue: METAMASK-GN3H

[danjm]

More context for metamask devs here

[sentry]

Sentry issue: METAMASK-GN54

[sentry]

Sentry issue: METAMASK-GN6H