zbus-lockstep v0.7.0

-## [0.7.0] - 2026-07-27

Most notable and breaking change is the Result<T> type alias returns a concrete LockstepError instead of a rype erased, boxed object.
For the base retrieval functions this means users can now conveniently match on LockstepError variants to handle an error.

Also zbus-lockstep does a better job distinguishing between In and Out-ward arguments if users lookup the type of an argument by name.
Before, if In and Out arguments had the same name users would receive the signature for first argument encountered with that name, which might be the wrong one.

Lastly, the lookup functions have been sped up, for what it is worth.

🔒️ Security / Secrets

• 🔒️ ci: harden github actions security (d60dd9e)

🐛 Fixes

• 🐛 fix: Colliding args names distinguishable by direction (8306c5a)

📝 Documentation

• 📝 docs: update release instructions (9235c45)
• 📝 docs: fix intra-doc links (8da2335)
• 📝 docs: update CHANGELOG.md (c2b3166)

♻️ Refactor / Move files

• ♻️ refactor: Adjust resolve_xml_path to concrete erros (0d12452)
• ♻️ refactor!: Result alias contains concrete Error type (27d1a54)
• ♻️ refactor: Always return concrete LockstepError from functions. (2ca38af)
• ♻️ refactor!: Name arg_name argument equally across fns (ff05116)
• ♻️ refactor: Avoid allocations / double conversions (75eb77b)

💄 Art and Style

• 🎨 Clippy: Alphabetic order in imports (65ac228)

✅ Testing and validation

• ✅ test: Add tests to demonstrate equal name args bug (2d78faf)

Full Changelog: v0.6.0...v0.7.0