Add npm, NuGet, and PyPI distribution for the xcrs binary

[Copilot]

Related Issue

Description

This branch was behind development and had drifted on release metadata. The update brings the PR current with the latest release/tooling changes and fixes the version-sync path so the xcrs package manifests stay aligned with the workspace version.

• Development sync

  • Merged the latest development into the PR branch
  • Pulled in current release/versioning updates already landed on the base branch

• Release metadata alignment

  • Updated xcrs npm and NuGet release metadata from 0.5.0 to 0.5.1
  • Kept the standalone xcrs distribution artifacts consistent with the workspace release version

• Version sync hardening

  • Replaced the workspace dependency version regex with section-aware entry parsing
  • Handles reordered version / path fields
  • Handles multiline inline-table formatting
  • Fails explicitly on malformed dependency entries instead of silently skipping them

if (entry.includes('path = "crates/') && entry.includes("version = ")) {
  return entry.replace(/version\s*=\s*"[^"]+"/g, `version = "${version}"`);
}

Type of Change

• Bug fix
• New feature
• Refactor (no functional change)
• Documentation update
• CI / tooling change

How Has This Been Tested?

Validated the merged branch against the relevant release/versioning checks and CI-equivalent workspace/package builds.

• cargo test --all-features
• Manual testing (smb <command>)

Checklist

• cargo check --workspace passes
• cargo clippy --workspace --tests -- -D warnings passes
• cargo fmt --all -- --check passes
• No new unwrap() or expect() calls in production code
• No new mod.rs files introduced
• New dependencies added to root Cargo.toml and inherited with { workspace = true }
• Error messages are user-friendly and surfaced to the terminal

Release Notes

• Improved xcrs release metadata synchronization so npm and NuGet artifacts stay aligned with the current workspace version after syncing with development.