feat(cli): new typescript projects use modern tsconfig (#429)

Changed target, module, moduleResolution, and lib to more modern TS
settings.

This sets a newer default, which prevents import errors when importing
other packages that use the `exports` map for defining entrypoints.

While the settings in this template will not fit all use-cases, it sets
a better example for future modifications (i.e. should specify
moduleResolution).

Fixes #427 

---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license

Author: iankhou

packages/aws-cdk/lib/init-templates/app/typescript/tsconfig.json

@@ -1,9 +1,10 @@
 {
   "compilerOptions": {
-    "target": "ES2020",
-    "module": "commonjs",
+    "target": "ES2022",
+    "module": "NodeNext",
+    "moduleResolution": "NodeNext",
     "lib": [
-      "es2020"
+      "es2022"
     ],
     "declaration": true,
     "strict": true,

packages/aws-cdk/lib/init-templates/lib/typescript/tsconfig.json

@@ -1,9 +1,10 @@
 {
   "compilerOptions": {
-    "target": "ES2020",
-    "module": "commonjs",
+    "target": "ES2022",
+    "module": "NodeNext",
+    "moduleResolution": "NodeNext",
     "lib": [
-      "es2020"
+      "es2022"
     ],
     "declaration": true,
     "strict": true,
@@ -25,6 +26,6 @@
   },
   "exclude": [
     "node_modules",
-    "cdk.out",
+    "cdk.out"
   ]
 }

packages/aws-cdk/lib/init-templates/sample-app/typescript/tsconfig.json

@@ -1,9 +1,10 @@
 {
   "compilerOptions": {
-    "target": "ES2020",
-    "module": "commonjs",
+    "target": "ES2022",
+    "module": "NodeNext",
+    "moduleResolution": "NodeNext",
     "lib": [
-      "es2020"
+      "es2022"
     ],
     "declaration": true,
     "strict": true,