fix(release): synchronize facade and macros versions

[alexhraber]

Summary

• publish the missed dactyl-db-macros 0.2.2 version through the normal release workflow
• keep dactyl-db and dactyl-db-macros in one release-plz version group
• include each package commits when calculating the other package release so changes to either member select the compatibility unit
• add regression coverage for manifest alignment and release configuration

Root cause

The green dactyl-db 0.2.2 release did not select dactyl-db-macros: release-plz reported that no macros commit matched release_commits, then treated its unchanged 0.2.1 manifest as already published. A green workflow therefore published only dactyl-db.

Verification

• cargo test --test release_configuration
• cargo test --all-targets --features "sqlite neon"
• cargo check --all-targets --features "sqlite neon"
• cargo clippy --all-targets --features "sqlite neon" -- -D warnings
• cargo fmt --all -- --check
• git diff --check
• container decapod validate: 184 passed, 0 failed