Cleaning up dependencies with cargo-machette

[theodorebugnet]

Description

Our makefile's install-dev-tools section installs cargo-udeps, but it seems broken because it requires a nightly compiler and it breaks sp1 crates when I tried it.

This PR replaces it with cargo machete, which is must faster and works fine, except it has a lot of false positives. Codex worked for some hours in the background adding [package.metadata.cargo-machete] sections to Cargo.toml files where necessary to get everything to compile again.

Net changes:

• -150 in Cargo.lock, a couple of dependency versions removed from the workspace
• Net minus in sp1 and risc0 crate Cargo.locks
• 10 completely unused dependencies removed from Cargo.toml
• A number of [package.metadata.cargo-machete] noise added to many Cargo.toml files
• With those metadata sections, cargo machete can run in CI for the future (once we update the Namespace base image)

• I have updated CHANGELOG.md with a new entry if my PR makes any breaking changes or fixes a bug. If my PR removes a feature or changes its behavior, I provide help for users on how to migrate to the new behavior.
• I have carefully reviewed all my Cargo.toml changes before opening the PRs. (Are all new dependencies necessary? Is any module dependency leaked into the full-node (hint: it shouldn't)?)

Linked Issues

• Fixes # (issue, if applicable)
• Related to # (issue)

Testing

Describe how these changes were tested. If you've added new features, have you added unit tests?

Docs

Describe where this code is documented. If it changes a documented interface, have the docs been updated?

Rendered docs are available at https://sovlabs-ci-rustdoc-artifacts.us-east-1.amazonaws.com/<BRANCH_NAME>/index.html

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.8%. Comparing base (18dbda9) to head (7492c08).
⚠️ Report is 56 commits behind head on dev.

Additional details and impacted files

see 48 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.