Fix #4958: Increase vitest timeout for Windows CI

[roomote]

Fixes #4958

Problem

The ShadowCheckpointService.spec.ts tests were timing out on Windows CI due to the default 10-second vitest timeout being insufficient. The tests involve heavy file system and git operations that can take longer than 10 seconds, especially on Windows CI environments.

Solution

• Added testTimeout: 20_000 and hookTimeout: 20_000 to the vitest configuration in src/vitest.config.ts
• Removed the redundant vitest.setConfig({ testTimeout: 10_000 }) call from the test file since timeout is now properly configured globally
• The hookTimeout configuration is crucial as the failure was specifically in the beforeEach hook

Testing

• All 30 tests in ShadowCheckpointService.spec.ts now pass locally in ~19 seconds
• The longest individual test takes ~882ms, well within the new 20-second timeout
• Type checking and linting pass successfully

This should resolve the Windows CI timeout issues while maintaining test reliability.

---

Important

Increase vitest timeout settings to 20 seconds in vitest.config.ts to fix Windows CI test timeouts.

• Configuration:
  • Increased testTimeout and hookTimeout to 20_000 in vitest.config.ts to address Windows CI timeouts.
  • Removed vitest.setConfig({ testTimeout: 10_000 }) from ShadowCheckpointService.spec.ts as global configuration now handles timeouts.
• Testing:
  • All tests in ShadowCheckpointService.spec.ts pass locally within the new timeout limits.
  • Type checking and linting pass successfully.

^{This description was created by for e605f5b. You can customize this summary. It will automatically update as commits are pushed.}