chore: commit the module resolution Next already enforces (#767)

next 16.2 rewrites tsconfig.json on every dev and build run, setting
moduleResolution to bundler, so the committed "node" value left every
checkout permanently dirty and reserialized without Prettier.

It also split resolution in two: CI type-checks a clean checkout with
node, which ignores package.json exports maps, while Vercel builds with
bundler, which honours them. That is how a private rainbowkit deep
import passed typecheck for months.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: rickstaa

tsconfig.json

@@ -17,7 +17,7 @@
     "noEmit": true,
     "esModuleInterop": true,
     "module": "esnext",
-    "moduleResolution": "node",
+    "moduleResolution": "bundler",
     "resolveJsonModule": true,
     "isolatedModules": true,
     "jsx": "react-jsx",