Add error utils

[mcmire]

This commit satisfies a few needs that we have in various projects:

• When catching a throwable from some kind of operation, we want to be able to test whether the throwable is an error.
• Furthermore, since the Error interface in TypeScript is pretty simple, we want to be able to test for different properties on an error (code, stack, etc.).
• We want to wrap an error produced by a lower level part of the system with a different message, but preserve the original error using the cause property (note: this property was added in Node 18, so for older Nodes, we use the pony-cause library to set this).
• Finally, we want to be able to take a throwable and produce an error that has a stacktrace. This is particularly useful for working with the fs.promises module, which (as of Node 20) does not produce proper stacktraces.

---

Places where we've used these kinds of utility functions:

• https://github.com/MetaMask/create-release-branch/blob/3556dee47163c921186051be7a1f3c98e2049db9/src/misc-utils.ts
• https://github.com/MetaMask/action-create-release-pr/blob/1359aa6b62c8e0b63aba994ec1bfb5210106a54d/src/utils.ts#L128
• https://github.com/MetaMask/core/blob/03f4256535e109eacfdac3afd5978c2a0f41926a/packages/network-controller/src/NetworkController.ts#L184
• https://github.com/MetaMask/github-tools/blob/033262110d7577b9288bb79f3b6c999dcf607bfc/src/fs-utils.ts#L6

---

Relates to MetaMask/module-lint#5.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
pony-cause	2.1.10	None	+0	23.9 kB	voxpelli

[MajorLift]

I wrote some test cases for error objects with multiple properties: 41aba60.

[Mrtenz]

A function to get an error message from an unknown error would be nice too. We use this in various places in Snaps at least.

[mcmire]

@Mrtenz I've added getErrorMessage. I took it from errors.ts in Snaps, but modified it to return an empty string for null and undefined. What do you think?

[mcmire]

@MajorLift I added your tests. There were a couple of duplicate tests that I removed as we discussed. I also added a test for isErrorWithStack that mimicked what you did for isErrorWithCode and isErrorWithMessage. Does that work?

[MajorLift]

Yes, the updates look good!

[mcmire]

@MajorLift ^ I pushed one more change, sorry!

[MajorLift]

LGTM!