fix: bump schema version so no_history migration runs on existing DBs

[timvisher-dd]

• Bump currentSchemaVersion from 7 to 8 so that initSchemaOnDB re-runs migrations on databases already at version 7. PR feat: add --no-history flag to separate Dolt commit skipping from GC eligibility #2622 added migration 011 (add_no_history_column) but did not bump the schema version, so existing databases take the fast path and skip RunMigrations, causing "column no_history could not be found" on every bd command.
• Replace global golangci-lint binary with go run in the pre-commit hook, pinned to v2.10.1. This ensures the linter is always compiled with the project's Go toolchain, eliminating panics when the global binary was built with an older Go than the runtime (e.g., golangci-lint built with 1.25 vs runtime 1.26).
• Fix versionChanges ordering in info.go — the 0.61.0 entry was appended at the end instead of prepended, breaking TestGetVersionsSinceOrder. Also merges two duplicate 0.60.0 entries into one.
• Add no_history column migration for embedded Dolt — the embedded Dolt schema migrations were missing the no_history column, causing all embedded Dolt CI tests to fail.

Test plan

• Run bd ready / bd ls against a .beads database created before the no_history column existed — succeeds without errors
• Verify schema_version in the config table is updated to 8 after first run
• Commit a .go file change and confirm the pre-commit hook runs go run golangci-lint successfully without requiring a global install
• TestGetVersionsSinceOrder passes
• CI: Embedded Dolt tests pass with new migration 0023
• CI tests pass (migrations are idempotent)

[codecov-commenter]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
4805	1	4804	548

View the top 1 failed test(s) by shortest run time

github.com/steveyegge/beads/cmd/bd::TestGetVersionsSinceOrder

Stack Traces | 0s run time

=== RUN   TestGetVersionsSinceOrder
    version_tracking_test.go:80: Versions not in chronological order: 0.61.0 (2026-03-15) should come before 0.57.0 (2026-03-01)
--- FAIL: TestGetVersionsSinceOrder (0.00s)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}