Update moduleResolution to bundler for exports field support

@actions/github@9 and @octokit/core@7 use package.json exports
subpaths which require moduleResolution bundler or node16+.
Using bundler with module esnext avoids ESM/CJS boundary issues
since ncc bundles the output into a single file regardless.

Author: ChanTsune

tsconfig.json

@@ -2,8 +2,10 @@
   "compilerOptions": {
     "target": "ES2022",
     /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019' or 'ESNEXT'. */
-    "module": "commonjs",
+    "module": "esnext",
     /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', or 'ESNext'. */
+    "moduleResolution": "bundler",
+    /* Specify module resolution strategy. */
     "outDir": "./lib",
     /* Redirect output structure to the directory. */
     "rootDir": "./src",