refactor(db): implement macro-based versioning system for database types

[kariy]

Summary

• Introduces a declarative macro system to simplify adding new database versions
• Reduces boilerplate from hundreds of lines to just a few lines per version
• Maintains full backward compatibility with existing databases

Problem

Currently, adding a new database version requires manually defining entire types, even if only a few fields changed. This creates hundreds of lines of boilerplate code and makes it error-prone to add new versions.

Solution

The new versioned_type! macro automatically generates:

• Versioned enum with all variants
• From trait implementations for conversions
• Compress and Decompress implementations with proper fallback chain
• Tests for backward compatibility

Changes

1. Added macro infrastructure (macros.rs):

   • versioned_type! macro for generating versioned enums
   • Automatic trait implementations for serialization/deserialization
   • Fallback chain for backward compatibility

2. Migrated existing types:

   • Transaction types (V6/V7) now use the macro
   • Block header types (V6/V7) now use the macro
   • All existing functionality preserved

3. Documentation:

   • Comprehensive README explaining the versioning system
   • Example file showing how to add new versions
   • Inline documentation for the macros

Example Usage

Adding a new version is now as simple as:

// Before: Hundreds of lines of boilerplate
// After: Just add one line
versioned_type! {
    VersionedTx {
        V6 => v6::Tx,
        V7 => v7::Tx,
        V8 => v8::Tx,  // New version added here
        V9 => katana_primitives::transaction::Tx,  // Latest
    }
}

Testing

• ✅ All existing tests pass
• ✅ Added tests for macro-generated code
• ✅ Verified backward compatibility with V6 data
• ✅ Round-trip serialization works correctly

Benefits

1. Minimal boilerplate: Adding versions reduced from ~200 lines to ~5 lines
2. Type safety: Compile-time verification of version compatibility
3. Automatic migration: Conversion code is generated automatically
4. Better maintainability: Clear separation of version-specific changes
5. Documentation: Self-documenting version history

🤖 Generated with Claude Code

[codecov]

Codecov Report

❌ Patch coverage is 96.57534% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 75.50%. Comparing base (9bde0ae) to head (4a32267).
⚠️ Report is 114 commits behind head on main.

Files with missing lines	Patch %	Lines
crates/storage/db/src/models/versioned/macros.rs	84.00%	4 Missing ⚠️
...rates/storage/db/src/models/versioned/block/mod.rs	98.64%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #273      +/-   ##
==========================================
+ Coverage   73.32%   75.50%   +2.18%     
==========================================
  Files         209      231      +22     
  Lines       23132    27234    +4102     
==========================================
+ Hits        16961    20564    +3603     
- Misses       6171     6670     +499     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.