Faster codebase indexing for huge repos (>500k files)

[In-line]

1. Moves codebase cache implementation to sqlite3 wasm DB
   a) This achieves better performance and avoids loading all of the paths in the JS heap (WASM heap is separate)
   b) We don't write all of the paths everytime (so no destroying user's SSD)
2. Progress popover for codebase now displays total files remaining, this is especially useful for repos with huge amount of files.
3. File processing is using queue and generator based implementation to avoid loading all of the objects into the JS heap at the same time.

Good candidate for test is built https://github.com/project-chip/connectedhomeip

Discord: .inline

[In-line]

Workspace tracker wasn't optimized currently

[roomote]

Rooviewer   See task

The latest commit addressed 5 of 6 previous issues. 1 prior issue remains unresolved; no new issues found.

• Deadlock on error in scanner: processTask does not call progressQueue.complete() on failure, causing the caller to hang indefinitely on for await (scanner.ts)
• Missing ripgrep kill in execRipgrep: ripgrep process is not killed when the queue limit is reached, so it runs to completion (or until the 10s timeout) even after the consumer stops reading (list-files.ts)
• Invalid PRAGMA journal_mode = WAL2: WAL2 does not exist in mainline SQLite/WASM; should be WAL (cache-manager.ts)
• Missing await on fileQueue.enqueue(): backpressure is ineffective in the scanner discovery loop (scanner.ts)
• NOT IN query exceeds SQLite variable limit on large repos: deleteHashesNotIn builds a single query with one placeholder per processed file; exceeds SQLITE_MAX_VARIABLE_NUMBER (32,766) well before the 50k file limit (cache-manager.ts)
• pendingBatchCount decrement uses .then() instead of .finally(): if a batch promise rejects, the counter never decrements and the while (pendingBatchCount >= MAX_PENDING_BATCHES) loop hangs (scanner.ts)

Previous reviews

• 615c3e5: Review #1
• 1e73dc7: Review #2
• 522eced: Review #3
• 51b3cf3: Review #4

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[In-line]