fix: exclude node_modules/.next from biome scanner, bump to 2.5.7

Biome's scanner walks node_modules and generated build output
(e.g. Next.js/Turbopack .next/dev chunks) regardless of files.includes,
which only governs lint/format targets, not the module-graph scanner.
On this monorepo (112k+ files under node_modules, actively regenerated
.next/dev artifacts) that let the biome daemon's memory grow unbounded
over a long-lived editor session.

Set files.experimentalScannerIgnores to exclude node_modules, .next,
.docker, and dist from the scanner, and bump @biomejs/biome from 2.1.1
to 2.5.7 to pick up several intervening scanner/module-graph fixes
(deadlock fix in 2.5.3, scanner-triggered memory fix in 2.5.2).

biome.json

@@ -16,7 +16,8 @@
 			"!node_modules/**",
 			"!packages/server/package.json"
 		],
-		"maxSize": 2097152
+		"maxSize": 2097152,
+		"experimentalScannerIgnores": [".next", "node_modules", ".docker", "dist"]
 	},
 	"assist": { "actions": { "source": { "organizeImports": "on" } } },
 	"linter": {