Resolve apiKeys test-file case collision on case-insensitive filesystems

[TechNickAI]

Problem

tests/unit/ tracked two files that differ only in case:

• db-apiKeys-crud.test.ts (camelCase, 542 lines / 54 tests)
• db-apikeys-crud.test.ts (lowercase, 188 lines / 8 tests)

On case-insensitive filesystems (macOS/APFS, default Windows) only one can exist in the working tree. A fresh git clone therefore warns:

warning: the following paths have collided ... and only one from the same
colliding group is in the working tree:

…and checks out just one of the pair, leaving the repo in a confused state (git status reports a phantom modification from the collision).

Fix

• Keep the canonical camelCase file — it matches src/lib/db/apiKeys.ts and the files=camelCase convention, and is the larger/maintained superset.
• Remove the lowercase duplicate.
• Port the 8 lowercase tests that covered behavior the superset was missing, so no coverage is lost:
  • malformed access_schedule JSON → null
  • throttleDelayMs / maxRequestsPerDay / maxRequestsPerMinute scalar fields
  • streamDefaultMode persistence
  • allowedCombos persistence
  • negative maxSessions clamped to 0
  • clearing scopes back to []
  • createApiKey defaults + sk-{machineId}- key format
• Add a test.after hook that closes the SQLite handle and removes the temp data dir, so the suite exits cleanly under the native runner (per CLAUDE.md → "Database Handles in Tests"). The canonical file previously leaked both.

Verification

node --test --test-force-exit tests/unit/db-apiKeys-crud.test.ts
ℹ tests 62
ℹ pass 62
ℹ fail 0

Exit code 0 (no hang). ESLint and Prettier clean.

Note

The same collision exists upstream in diegosouzapw/OmniRoute (identical blobs) and has not been fixed there. This PR can be ported upstream if desired.

[TechNickAI]

Closing in favor of upstream diegosouzapw#3125 (merged 2026-06-03 by @juandisay), which already removed the lowercase case-variant duplicate. The fork will pick up that fix on its next sync from upstream. Note: diegosouzapw#3125 deleted the lowercase file without porting its unique test coverage, so that coverage won't carry over — accepted as upstream's approach.