Test suite intermittently fails on Windows with 'EBUSY: resource busy or locked'

[Zireael]

Describe the bug
The test suite intermittently fails on Windows environments with EBUSY: resource busy or locked errors during teardown. This happens when attempting to clean up temporary directories containing SQLite databases using rmSync(dir, { recursive: true, force: true }).

To Reproduce
Run the test suite on a Windows machine. The failures are intermittent but frequent in tests that utilize real OpenCode DB harnesses (e.g., tests dealing with compartments and DB storage).

Root Cause
SQLite file handles take a moment to be fully released by the OS/driver after closing the database connections. Windows, unlike POSIX systems, strictly locks these files and prevents immediate directory deletion.

Workaround/Fix
Wrapping rmSync calls in afterEach hooks with try/catch blocks (to ignore EBUSY) and adding maxRetries: 10 and retryDelay: 100 options allows the handles to release properly and mitigates the issue.

[alfonso-magic-context]

Fixed via #104 (thanks @Zireael) — merged to master. Test teardown now wraps the temp-dir rmSync cleanup in try/catch with maxRetries/retryDelay, so a brief Windows file lock on a SQLite DB file no longer fails the suite during afterEach.

Note: the recent node:sqlite migration also removed better-sqlite3 as a runtime dependency, so the native .node-binding half of the lock cause is gone — this handles the remaining DB-file handle lingering. Ships in the next patch release.