Fix state migration version collision

[andrei-hasna]

Fix-forward for canonical incident 693334 after PR #528 merged before fixed Erdos completed review.

This candidate moves the usage-profile lease migration from SQLx version 0068 to 0069, preserving the existing thread-monitor authorization migration at 0068. It adds focused regressions on the real StateRuntime initialization path for:

• a fresh SQLite state database; and
• an existing database already stamped with the prior thread-monitor authorization migration at version 0068.

Local lightweight evidence:

• cargo fmt: exit 0 (stable rustfmt ignored the optional nightly imports_granularity flag)
• migration version control: duplicate_versions=0, version_0068=1, version_0069=1
• staged Shield review: No security issues found in staged changes, exit 0
• exact-range Gitleaks origin/main..HEAD: 1 commit scanned, no leaks found, exit 0

No local Rust test or Bazel build was run. Required affected Rust CI, Required Bazel/BuildBuddy, and full Blacksmith Testbox gates remain pending on this exact head. Fixed Erdos focused re-review remains pending until those gates are terminal green.

Todos: a59d3086-a01e-4152-b315-aee3ca2e470f
Canonical incident: 693334
Remediation cycle: 1

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[andrei-hasna]

Closed as a preserved semantic duplicate. The user explicitly continued the existing task worktree/branch, so PR #532 at cb617b4 is the sole R5 candidate. This branch is not deleted; no merge/release/install action is authorized.