fix(e2e): pass explicit --config to wrangler dev to avoid config ambiguity

vite build generates dist/server/wrangler.json; wrangler auto-discovers
it alongside .wrangler/deploy/config.json and refuses to proceed.
Passing --config wrangler.jsonc explicitly resolves the ambiguity.

Author: anulman

playwright.config.ts

@@ -11,7 +11,7 @@ export default defineConfig({
     // In CI, serve the built Worker + static assets via wrangler (instant, no compilation).
     // Locally, use the vite dev server for HMR.
     command: isCI
-      ? "bunx wrangler dev dist/server/server.js --assets dist/client --port 3000 --compatibility-date 2025-09-02 --compatibility-flag nodejs_compat"
+      ? "bunx wrangler dev dist/server/server.js --config wrangler.jsonc --assets dist/client --port 3000 --compatibility-date 2025-09-02 --compatibility-flag nodejs_compat"
       : "bun run dev",
     url: "http://localhost:3000",
     reuseExistingServer: !isCI,