fix(hoosage): read Copilot CLI sessions from WSL on Windows

[wakemeup0]

Problem

When a WSL folder is opened in Windows VS Code (\\wsl.localhost\<distro>\...), hoosage runs on Windows and only reads the Windows ~/.copilot/session-state. Copilot CLI sessions started inside the WSL distribution (/home/<user>/.copilot/session-state) were never counted, so WSL projects showed far too little CLI usage.

Fix

• New WslCliSessions (src/core/wsl-sessions.ts): on Windows, lists running distributions via wsl.exe --list --running --quiet right before reading (normally every 15 s), so a stopped distribution is never started. Discovers /root and /home/* .copilot/session-state via \\wsl.localhost\<distro> and reuses CliUsageScanner per folder.
• Linux cwds are translated before project matching: /home/u/repo → \\wsl.localhost\<distro>\home\u\repo, /mnt/c/repo → C:\repo. WSL CLI sessions therefore join the project of the WSL folder opened in Windows VS Code.
• Usage read earlier stays visible while a distribution is stopped. Stopped distributions do not hold up indexing.
• Shared-sync entries whose id was already read locally are skipped, so a peer WSL host sharing the same sessions is not double counted.
• New setting hoosage.readWslCliSessions (default true). Diagnose Tracking reports the number of WSL session folders read.

Verification

• npm run check passes (75 tests, including 4 new ones in test/wsl-sessions.test.ts).
• Real data: 215 CLI calls (~$402.70) from a running VRKB distribution resolve to the project of \\wsl.localhost\VRKB\home\<u>\src\vrkb. Previously none of them were visible.