feat: Change version numbering of c2patool to match c2pa-rs crate

[scouten-adobe]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.39%. Comparing base (36eeab8) to head (1ed58af).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1648   +/-   ##
=======================================
  Coverage   75.39%   75.39%           
=======================================
  Files         167      167           
  Lines       37759    37759           
=======================================
  Hits        28467    28467           
  Misses       9292     9292           

☔ 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.

[codspeed-hq]

CodSpeed Performance Report

Merging #1648 will not alter performance

_{Comparing c2patool-version-match (1ed58af) with main (36eeab8)}

Summary

✅ 16 untouched
⏩ 2 skipped¹

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[ok-nick]

What are the benefits to sharing a version number here? I see that updating c2pa-rs will almost always warrant an update to c2patool, but for the reverse, an update to c2patool likely doesn't make sense to update c2pa-rs. What happens when we make a breaking change to c2patool, does that mean we need to make a breaking change to c2pa-rs? (when we hit 1.0, is this still true?)