chore!: bump TypeScript target and lib to ES2022

[cryptodev-2s]

Top of stack #331, on #325. Mirrors MetaMask/core#10019, the last of core's foundational chain.

	Before	After
target	ES2020	ES2022
lib	["ES2020", "DOM"]	["ES2022", "DOM"]

Correctly last in the order: raising the emit target is only defensible once the Node floor guarantees the runtime supports it, which #328 established.

It is not cosmetic

wrapError sets cause behind two @ts-ignore comments, with this note in the source:

Error causes are not supported by our current tsc target (ES2020, we need ES2022 to make this work)

Error.cause is ES2022, so both suppressions are now obsolete and are removed. The types are genuine rather than ignored.

The evidence came from enabling test type checking: with lib: ES2020 a tsc pass over the tests reports 11 errors, nearly all Property 'cause' does not exist. With lib: ES2022 it reports zero. That is why the type checking PR stacks on top of this one rather than below it.

Verification

Build, tests, tsd, eslint and lint all pass.

---

Note

Medium Risk
Breaking for consumers on older runtimes or TS configs that assumed ES2020 output; error utilities are widely used but the change is configuration and type hygiene rather than new logic.

Overview
BREAKING: Raises the TypeScript target and lib from ES2020 to ES2022, so published output expects a modern runtime or bundler that can consume ES2022. The unreleased changelog documents this alongside the existing Node/ESM breaking changes.

In wrapError, the Error(message, { cause }) path no longer needs @ts-ignore or the comment about ES2020 lacking Error.cause types—ES2022 lib makes cause a first-class typed option.

No runtime behavior change in wrapError beyond what was already implemented; this is primarily a compile/emit floor and type-checking cleanup that unblocks stricter test tsc (e.g. cause on errors) in follow-up work.

^{Reviewed by Cursor Bugbot for commit 6242b3e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Mrtenz]

Suggested change

	- **BREAKING:** Bump the TypeScript `target` and `lib` to `ES2022` ([#332](https://github.com/MetaMask/utils/pull/332))
	- Emitted output now uses ES2022 syntax, matching core. Consumers on the supported Node range are unaffected.
	- **BREAKING:** Bump TypeScript target to ES2022 ([#332](https://github.com/MetaMask/utils/pull/332))
	- This package now ships ES2022 code, requiring a compatible modern environment or bundler configuration to consume.

[cryptodev-2s]

done here 475c5c9