Revert "remove rust-version from fuzz"

[xtqqczze]

uufuzz is published on crates.io, so we shouldn't remove rust-version from the package metadata.

[codspeed-hq]

Merging this PR will improve performance by 3.73%

⚡ 1 improved benchmark
✅ 356 untouched benchmarks
⏩ 50 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	Simulation	du_deep_tree[(100, 3)]	2.1 ms	2 ms	+3.73%

Tip

Curious why performance improved? Comment @codspeedbot explain why performance improved on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing xtqqczze:rust-version (814aa6b) with main (9986da4)}

Footnotes

1. 50 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. ↩

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/tail/symlink (fails in this run but passes in the 'main' branch)

[oech3]

Sorry. I don't understand. We can guarantee build with latest stable Rust without that metadata.

[sylvestre]

@xtqqczze wdyt? :)

[sylvestre]

in fuzz/ cargo publish --dry-run --workspace passed

[xtqqczze]

@xtqqczze wdyt? :)

I don't see why we should remove rust-version from the package metadata, given that uufuzz is published.

[oech3]

I think we need to keep rust version of production small for legacy distributions with disadvantage of restriction for modern APIs. But we don't need to restrict modern APIs for test code.

[xtqqczze]

But we don't need to restrict modern APIs for test code.

I think we can keep rust-version in uufuzz and bump it if we need to.