build(deps): update cargo-rail to 0.29.0

[loadingalias]

Summary

• update Cargo-Rail from 0.28.1 to 0.29.0
• reduce the config to Eryx’s explicit target, exclusion, and MSRV policies
• remove the obsolete affected task and stale implementation plan
• leave the existing paths-filter integration unchanged

Validation

• cargo rail config validate --strict
• cargo rail config explain --all -f json
• mise run unify-check — dependencies are coherent
• formatting and Clippy pass
• 641/642 tests pass on my MacBook Pro (M1) - the existing x86 CPU feature test fails obviously

Feedback

Cargo-Rail reports the workspace deps are coherent while preserving the eryx-wasm-runtime and eryx-macros exclusions.
I am really just submitting the PR to help update Cargo-Rail and to understand your usage. I wanted to ask for direct feedback, as well. What isn't Cargo-Rail doing well that you'd expected? What do you like or dislike? What's not working as you'd expected or what have you found that's not correct?

I genuinely appreciate the feedback! I was also thinking... for a follow up Cargo-Rail-Action migration, which CI decisions would you want Cargo-Rail to own? Let me know! Feel free to reach out or open issues, discussions, etc.

[sd2k]

Hey @loadingalias! It looks like my renovate cronjob auto-approved and merged the renovate PR doing the same thing, I appreciate you reaching out and updating the config though, would happily merge that if you could fix the conflicts.

The main reasons I switched to cargo-rail were documented in the doc/plan in this PR: unifying dependencies, pruning dead features, detecting unused dependencies, and computing the MSRV. So far it's been working pretty well as far as I can tell. I haven't noticed anything wrong, and generally if something is quietly working then I'm happy!