fix(build): tolerate trailing commas when reading wrangler.jsonc

After the D1 migration succeeds, migrate-production.mjs calls
wranglerD1DatabaseIds() -> readWranglerConfig(), which did
JSON.parse(stripJsonComments(text)). strip-json-comments removes comments but
not trailing commas, so wrangler.jsonc (e.g. `"binding": "ASSETS",` before `}`)
threw 'Expected double-quoted property name in JSON'. Strip trailing commas too.

Surfaced now that the Cloudflare build gets past migrate (Node 24 pin + D1
adapter wiring): the D1 schema migration runs and succeeds, then this parse ran.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: ceccec

scripts/lib/wranglerConfig.mjs

@@ -1,5 +1,8 @@
 /**
- * Parse `wrangler.jsonc` once per process (comments stripped — valid JSON only after strip).
+ * Parse `wrangler.jsonc`. `.jsonc` permits both comments and trailing commas; `strip-json-comments`
+ * removes only comments, so we also strip trailing commas (a `,` right before `}`/`]`) before
+ * JSON.parse — otherwise a config like `"binding": "ASSETS",\n}` throws "Expected double-quoted
+ * property name".
  */
 import fs from 'node:fs'
 import path from 'node:path'
@@ -10,7 +13,8 @@ import stripJsonComments from 'strip-json-comments'
 export function readWranglerConfig(cwd = process.cwd()) {
   const p = path.join(cwd, 'wrangler.jsonc')
   const text = fs.readFileSync(p, 'utf8')
-  return JSON.parse(stripJsonComments(text))
+  const json = stripJsonComments(text).replace(/,(\s*[}\]])/g, '$1')
+  return JSON.parse(json)
 }
 
 /**