fix: Node.js v25 / Windows compatibility and locale-aware number formatting

[smitt14ua]

Summary

Fixes three test failures that appear when running npm test locally on Windows with Node.js v25 (CI uses Ubuntu + Node.js v24 where none of these manifest):

• localStorage.getItem is not a function — Node.js v22.12+ exposes a native localStorage global (SQLite-backed in v25).
  Without --localstorage-file the object exists but its methods are not functions, silently overriding jsdom's storage mock.
  testSetup.ts now detects this and replaces the broken global with a plain in-memory Storage implementation.
• TypeError: … Received 'file:///@solid-refresh' — vite-plugin-solid registers /@solid-refresh as a virtual module ID; vitest 4 converts it to file:///@solid-refresh. On Windows, fileURLToPath rejects that URL because the path has no drive
  letter. A new enforce: "pre" plugin in vitest.config.ts intercepts the ID and returns the real file path before solidPlugin can register the virtual one. Also removes the deprecated poolOptions block (removed in vitest 4).
• Wrong thousands separator in tests — MapDetail.tsx called toLocaleString() without a locale, so on a non-English Windows machine 30720 rendered as "30 720" instead of "30,720". Now passes locale() from useI18n() explicitly.

How to test

  cd ui && npm test

Optionally verify on Windows with Node.js v25 — previously produced 40 failed test files and 9 failed tests.

Checklist

• go test ./... passes
• cd ui && npm test passes (if frontend changed)
• No breaking changes (or documented below)

[gemini-code-assist]

Code Review

This pull request introduces localization for world size formatting in the Map Detail view and addresses environment-specific issues in the test suite. Key changes include a localStorage polyfill for Node.js environments where the native global is incomplete and a Vitest configuration fix for Windows-specific path resolution of @solid-refresh. Feedback was provided to improve the localStorage polyfill by using a null-prototype object for the internal store to prevent collisions with inherited properties.

[fank]

Reviewed the diff and ran npm test locally — 1498/1498 pass. All three fixes look correct:

• MapDetail.tsx: useI18n() returns locale as an Accessor signal (ui/src/i18n/i18n.ts:34), so locale() is the right call.
• testSetup.ts: the getItem !== "function" probe correctly identifies the broken Node 25 native localStorage and swaps in an in-memory Storage.
• vitest.config.ts: enforce: "pre" ensures the redirect runs before vite-plugin-solid's resolveId claims the virtual ID. require.resolve("solid-refresh/dist/solid-refresh.mjs") works because solid-refresh exports ./dist/*. Minor nit — require.resolve("solid-refresh") would resolve via the import condition and be a bit less fragile to file renames, but the explicit path is fine.

Same Windows locale bug elsewhere

The thousands-separator fix in MapDetail.tsx patches one site, but the identical pattern exists in ui/src/pages/recording-selector/DetailSidebar.tsx at lines 128, 132, 136, 140, 168, 176 — six bare toLocaleString() calls (units, alive, dead, kills, playerKills). On a German Windows host these will render "30 720" and would break the same kind of test assertion this PR is fixing. Worth including here for consistency, or filing a follow-up.

[smitt14ua]

I think I'll make same changes for these components as well, so I'm moving this PR into draft