fix(packages): reorder exports conditions to prevent Node.js .ts resolution

Node.js v20.20.1 is matching the `types` export condition before `default`,
causing ERR_UNKNOWN_FILE_EXTENSION when it tries to load .ts source files
at runtime. Moving `default` before `types` ensures Node.js resolves to
the compiled .js output first. TypeScript explicitly seeks the `types`
condition regardless of key order, so TS resolution is unaffected.

Fixes the API container CrashLoopBackOff in the groombook namespace.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

packages/db/package.json

@@ -7,8 +7,8 @@
   "types": "./src/index.ts",
   "exports": {
     ".": {
-      "types": "./src/index.ts",
-      "default": "./dist/index.js"
+      "default": "./dist/index.js",
+      "types": "./src/index.ts"
     }
   },
   "scripts": {

packages/types/package.json

@@ -7,8 +7,8 @@
   "types": "./src/index.ts",
   "exports": {
     ".": {
-      "types": "./src/index.ts",
-      "default": "./dist/index.js"
+      "default": "./dist/index.js",
+      "types": "./src/index.ts"
     }
   },
   "scripts": {