fix(init): emit ESM-compatible tsconfig for TypeScript projects (#5596)

`codecept init` installs tsx and sets `require: ['tsx/cjs']`, but the
generated tsconfig.json still carried the legacy ts-node setup:

- a `"ts-node": { files: true }` block, though ts-node is never installed
  and is marked "not recommended" in loaderCheck.js
- `"module": "commonjs"`, wrong for an ESM ("type": "module") project

Generate a tsconfig that matches the tsx/ESM setup init already configures:
drop the ts-node block, use `module: ESNext` with `moduleResolution: bundler`
(so extensionless imports resolve as tsx/docs expect), and bump target/lib
to ES2022.

Co-authored-by: DavertMik <davert@testomat.io>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Author: 3 people

lib/command/init.js

@@ -245,14 +245,12 @@ export default async function (initPath, options = {}) {
     }
 
     const tsconfig = {
-      'ts-node': {
-        files: true,
-      },
       compilerOptions: {
-        target: 'es2018',
-        lib: ['es2018', 'DOM'],
+        target: 'ES2022',
+        lib: ['ES2022', 'DOM'],
         esModuleInterop: true,
-        module: 'commonjs',
+        module: 'ESNext',
+        moduleResolution: 'bundler',
         strictNullChecks: false,
         types: ['codeceptjs', 'node'],
         declaration: true,