core: support ts targets before es2022

[adamraine]

Fixes #15186

It's a pretty simple fix, but the options param on Error was first added in Node 16 which is our minimum node version. If someone encounters a type error like in #15186, is that just a sign that their ts target is too old for us to support?

[brendankenny]

It seems ok? As you said, it's a simple fix, so why not. Maybe add an explicit TODO to remove in LH11 or whenever, though, so it's clear that it can be removed at some point.

Sooner or later we're going to want to include other features in the es2022 lib (there's not much else in that one, but there's at least [].at()/''.at()), but since we publish types now, we could maybe make sure to align bumping tsc target versions with when we bump node version requirements so we don't catch people like this.