fix: don't write beta version in WriterVersion

[wjones127]

This is a forwards compatibility fix. Earlier versions of Lance expected the version string to exclusively be X.Y.Z, but newer versions were writing with X.Y.Z-beta.N sometimes. This caused writers on earlier versions to panic when writing, making the tables unwriteable.

This is a companion to #5111, which made it so we don't panic if we encounter a version we can't parse.

Testing

I validated locally by:

• Commenting out the Rust change to omit the prerelease version
• Changing the current Rust library version to be a prerelease
• Running datagen with current version
• Running forward compat tests with pylance==0.36.0

Got:

thread '<unnamed>' panicked at /Users/runner/work/lance/lance/rust/lance-table/src/format/manifest.rs:513:32:
Invalid writer version: 0.38.3-beta.1

The tests pass with the fix.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.68%. Comparing base (056062a) to head (9814d94).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5113      +/-   ##
==========================================
- Coverage   81.71%   81.68%   -0.03%     
==========================================
  Files         340      340              
  Lines      138910   138912       +2     
  Branches   138910   138912       +2     
==========================================
- Hits       113506   113474      -32     
- Misses      21667    21702      +35     
+ Partials     3737     3736       -1     

Flag	Coverage Δ
unittests	81.68% <100.00%> (-0.03%)	⬇️

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

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

[jackye1995]

lol I also published the fix to continue to record the beta version here - #5116, I think that includes the change here

[westonpace]

How does this relate to #5116 ?

[wjones127]

Closing in favor of #5116