[Advancement] Migrate local history DB with explicit schema versioning

[Nanle-code]

Objective

Ensure the local history/analytics database uses explicit schema versions and tested migrations.

Target area

src/utils/database.rs

Context

Local DB upgrades must be crash-safe and reversible where possible.

Requirements

• Schema version table/metadata
• Forward migrations with tests
• Backup-before-migrate option

Acceptance criteria

• Migrations tested from N-1 to N
• Corrupt DB detection fails clearly
• Docs describe recovery

Pull request merge requirements

Pull requests that resolve this issue must not be merged until all of the following are true:

1. All required CI checks are green on the latest commit of the PR (build, tests, lint/format, and any workflow jobs required by branch protection).
2. The branch has no merge conflicts with the target branch (master / default), and a clean merge or rebase is possible without unresolved conflicts.
3. Review feedback is addressed, and the change remains focused on this issue’s acceptance criteria.

Contributors should run the local CI-equivalent checks before opening or updating the PR (see CI_ENFORCEMENT.md and CONTRIBUTING.md).

[emmyafolly123-coder]

@emmyafolly123-coder has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer! I’m interested in working on this task and can deliver a clean solution within the required timeframe

ℹ️ Repo Maintainers: To accept this application, review their application or assign @emmyafolly123-coder to this issue.