fix: resolve failing frontend tests and test environment issues

[zinodict121]

Fix Failing Frontend Tests and Test Environment Issues

Description

This PR resolves several critical test suite failures in the frontend utility project, ensuring that the test environment is fully stable across platforms and that there are no infinite layout loops during component tests.

Closes #181

Changes Made

• Pre-Commit Hook Parsing: Removed the bash hashbang (#!/usr/bin/env node) from scripts/pre-commit.mjs. Vite's strict ES Module parser (Rolldown) was choking on it when imported in tests/unit/preCommit.test.ts.
• Windows Command Execution: Fixed ENOENT errors in scripts/setup-dev.ts by appending { shell: process.platform === "win32" } to execFileSync("npm", ...). This ensures .cmd scripts are resolved properly on Windows.
• Infinite Layout Loop in VirtualList: Fixed the Maximum update depth exceeded error in src/components/ui/VirtualList.tsx. The createMeasureRef factory was previously returning a new function reference every render, creating a detachment/attachment loop. It now uses a stable useRef dictionary. Additionally, useVirtualList.ts now safely ignores 0-height measurements (common in jsdom) to prevent layout thrashing.
• Synchronous Mocks in Hook Tests: Fixed a scroll state bug in tests/hooks/useVirtualList.test.ts.
  • The hook test now properly simulates window scrolling by supplying useContainerScroll: false.
  • Added a defensive check to handleScroll to prevent synchronous test mocks from unintentionally locking the requestAnimationFrame queue reference.
• Setup Dev Mocks: Added a structural mock for node:child_process in tests/unit/setupDev.test.ts to prevent the unit test from timing out while attempting to run actual npm scripts.

Verification

• Verified all 86 test suites and 705 tests pass successfully (npm run test).
• Verified local development setup script executes correctly across both Windows and Unix environments.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update