fix(web): set NODE_ENV to production in start script

The "start" script now explicitly sets NODE_ENV to "production". This
 ensures the application runs in the correct environment, avoiding
 potential issues caused by an undefined NODE_ENV variable.

apps/web/package.json

@@ -74,7 +74,7 @@
 		"format": "biome check --vcs-enabled=true --vcs-use-ignore-file=true  --formatter-enabled=true --linter-enabled=false --organize-imports-enabled=true .",
 		"format:write": "biome check --vcs-enabled=true --vcs-use-ignore-file=true  --formatter-enabled=true --linter-enabled=false --organize-imports-enabled=true --write .",
 		"lint": "biome ci --vcs-enabled=true --vcs-use-ignore-file=true --vcs-root='../../' --formatter-enabled=false --linter-enabled=true --organize-imports-enabled=false --no-errors-on-unmatched .",
-		"start": "node --experimental-strip-types --experimental-transform-types server/server.ts build/server/index.js",
+		"start": "NODE_ENV=production node --experimental-strip-types --experimental-transform-types server/server.ts build/server/index.js",
 		"test": "vitest",
 		"test:unit": "vitest",
 		"typecheck": "react-router typegen && tsc"