ci: reconcile release workflows with the development repository

[suchintan]

The release workflows here and in the development repository are maintained by hand and had drifted in both directions. Releases are cut from tags on this repository, so these are the copies that actually run.

This applies the union of both sides' fixes to the three files that differed:

• release-gem.yml — compare versions as parsed Gem::Version values. RubyGems rewrites a SemVer prerelease (0.3.0-beta.1 becomes 0.3.0.pre.beta.1), so the current raw-string comparison would abort the next prerelease gem release with a false "versions do not match".
• release-maven.yml — newer pinned actions/setup-java (v5.6.0).
• release-nuget.yml — spacing normalization only.

The matching change on the development side has already merged, leaving the shared workflow files byte-identical in both repositories. release-npm.yml and release-pypi.yml already matched.

🤖 Generated with Claude Code

[claude]

Summary

Small, well-scoped CI-only change reconciling release workflows with the development repo. The gem version-comparison fix is correct and the accompanying comments clearly explain the reasoning; Maven/NuGet changes are trivial. No core (Rust/Python/Node) code is touched, so most FFI/CDP/security review categories don't apply here.

🔴 Critical Issues (0)

None found.

🟡 Suggestions (1)

• release-gem.yml: Gem::Version.new(cargo_version) will raise ArgumentError (uncaught, since the script runs under set -euo pipefail) if Cargo.toml's version string is ever malformed or empty (e.g. the regex extraction fails and cargo_version is nil). Not a regression from this PR, but since the line is being touched anyway, consider guarding with abort 'Unable to parse Cargo.toml version' before constructing Gem::Version.new for a clearer failure message than a raw Ruby backtrace.

📝 Minor / Style (1)

• The PR description mentions the matching change already merged in the development repo, and that release-npm.yml/release-pypi.yml already matched — nice due diligence. No action needed, just confirming that's reflected in the diff (only the 3 files listed are touched).