fix(store): upgrade exact legacy v97 databases

[Qiyuanqiii]

Summary

• accept only the exact pre-final Windows preview checksum for migration v97
• add schema v125 to transactionally restore the canonical Docker lifecycle cleanup trigger while preserving the historical v97 row
• extend the cumulative historical migration fixture chain and document that the portable ZIP still uses the shared user data home

Safety boundary

• no database deletion, reset, or checksum rewriting
• unknown checksums, wrong names, migration gaps, and newer histories still fail closed
• published v0.1.0-rc.2 assets remain immutable; this repair is intended for a later prerelease

Validation

• targeted v97/v125 migration and rejection tests
• go test ./internal/store -count=1 -timeout 30m (passed in 756.866s)
• go vet ./internal/store
• 289 frontend tests plus production renderer build
• Desktop Go/Wails tests and reproducible production-tag EXE build
• final EXE launched against a temporary copy of the affected legacy database, upgraded it to v125 with PRAGMA integrity_check = ok, preserved the v97 checksum, and left the source database hash unchanged

Release follow-up

After required PR checks pass and this PR is merged, publish v0.1.0-rc.3 only through the tag-triggered Desktop release workflow.

[Qiyuanqiii]

CI follow-up: the first Go job had no assertion failure; internal/store was interrupted exactly at the existing 30-minute package timeout. The rc.2 main run completed Store in 1050.129s, while the v125 run reached 1800.133s under shared-runner contention. Commit b971634 raises the still-bounded complete-suite timeout to 45 minutes without skipping, caching, or narrowing any test. All other CI jobs and the full Desktop release candidate workflow passed on the first attempt.