build: declare the ES2022 standard library in the tsconfigs

The lib declarations (es2018/es2019) understate every runtime this
project supports — Node 20+ and the browsers Angular 21 supports all
provide ES2022, and the Angular CLI generates new workspaces at ES2022.
This also resolves the inconsistency of target es2020 sitting alongside
lib es2018.

Type-checking declaration only; compilation targets are unchanged, so
emitted code is identical.

Author: armando-navarro

tsconfig.base.json

@@ -18,7 +18,7 @@
         "node_modules/@types"
       ],
       "lib": [
-        "es2018",
+        "es2022",
         "dom"
       ],
       "paths": {

tsconfig.build.json

@@ -5,7 +5,7 @@
     "compilerOptions": {
         "outDir": "tools",
         "skipLibCheck": true,
-        "lib": ["es2019", "dom"],
+        "lib": ["es2022", "dom"],
         "module": "commonjs",
         "target": "ES2020",
         "plugins": [

tsconfig.json

@@ -11,7 +11,7 @@
     ],
     "lib": [
       "dom",
-      "es2018"
+      "es2022"
     ]
   },
   "angularCompilerOptions": {