fix: Add version to truss-core dep for crates.io publishing

[jeanclawdbotdamn]

Summary

• The truss-cli publish step in the v0.1.0 release failed because Cargo.toml had a path-only dependency on truss-core without a version specifier
• crates.io requires all dependencies to have a version when publishing
• Adds version = "0.1.0" alongside the existing path for truss-core

Error from CI

error: failed to verify manifest
Caused by:
  all dependencies must have a version requirement specified when publishing.
  dependency `truss-core` does not specify a version

After merging

To publish truss-cli to crates.io, either:

1. Delete and re-push the v0.1.0 tag to re-trigger the release workflow, or
2. Run cargo publish -p truss-cli manually with the registry token

Test plan

• cargo fmt --check passes
• cargo clippy --workspace -- -D warnings passes
• cargo test --workspace passes

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.65%. Comparing base (c090f90) to head (6cc0982).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #42   +/-   ##
=======================================
  Coverage   77.65%   77.65%           
=======================================
  Files          50       50           
  Lines        4408     4408           
=======================================
  Hits         3423     3423           
  Misses        985      985           

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.