Stamp v1 version when converting a v0 config with musica-cli

[K20shores]

Problem

musica-cli --convert <v0-config> -o out.json produces a v1-structured mechanism, but the output is stamped "version": "0.0.0". convert_configuration does parse() then export(), and the v0 parser stamps the mechanism version as 0.0.0. On the next load, Parse() reads that version and dispatches to the v0 parser, which then looks for camp-files and fails — the converted file is v1-structured.

This blocks the intended workflow of converting a v0 config and embedding the result as an inline mechanism in a music_box v1 configuration.

Fix

Re-label the mechanism as 1.0.0 in convert_configuration before export, since the command's job is to emit a v1 document. Added a test asserting the exported file carries "version": "1.0.0".

Note: fully round-tripping a v0 config to a loadable v1 mechanism also needs the companion v0-parser fixes in NCAR/MechanismConfiguration#309 (diffusion coefficient, merged) and NCAR/MechanismConfiguration#310 (THIRD_BODY, per-reaction gas phase, surface-name prefix). This PR addresses only the version stamp.

🤖 Generated with Claude Code

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.04%. Comparing base (0e9e356) to head (3ce0943).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #983      +/-   ##
==========================================
+ Coverage   71.83%   72.04%   +0.20%     
==========================================
  Files         135      135              
  Lines       11631    11632       +1     
==========================================
+ Hits         8355     8380      +25     
+ Misses       3276     3252      -24     

Flag	Coverage Δ
cpp_fortran	62.96% <ø> (ø)
javascript	94.59% <ø> (ø)
python	74.18% <100.00%> (+0.51%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 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.