fix(NoTicket): remove password hashes from token cache filenames

[lorenzhs]

Use identity-based, versioned cache filenames and discard legacy cache files, including those left after credential rotation. Do not migrate old tokens.

Cover cache isolation, cleanup, and wrong-password handling. Isolate real-filesystem unit test fixtures from the user token cache.

---

Note

Medium Risk
Changes on-disk token cache layout and deletes legacy cache files on startup, forcing re-auth for affected users; encryption still depends on password for read access.

Overview
Token cache files are renamed so filenames no longer embed a password hash—only a username-derived token-v2-{hash}.json path is used. On TokenSecureStorage init, legacy 64-hex-char.json cache files are deleted (no token migration), so users with old caches must sign in again.

A password change for the same username now hits the same cache file but cannot decrypt the stored token (expected). Tests cover filename stability, legacy cleanup, and that unrelated files/dirs in the cache folder are left alone. Unit tests that use the real filesystem get an autouse fixture that redirects user_data_dir to tmp_path.

^{Reviewed by Cursor Bugbot for commit 19984f8. Bugbot is set up for automated code reviews on this repo. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
90.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud