build: Add xtask automation for binding version management

[anakrish]

Introduces a dedicated xtask crate that keeps language binding versions in sync with the core regorus crate, following the workflow pattern used by rust-analyzer, gitoxide, and ripgrep.

Key features:

• Git-based change detection: compares binding source files against a base ref (merge-base with origin/main by default) plus unstaged/ untracked files to identify which bindings have been modified
• SemVer-aware bumping: binding edits trigger a minor version increment (e.g. 0.5.1 → 0.6.0) under pre-1.0 semantics, signaling potential breaking changes; clean bindings simply align to the root version
• Multi-language support: updates Cargo manifests (Rust FFI, Java, Python, WASM, Ruby), Maven pom.xml (Java), Ruby version constants, and C# project files in a single pass
• CI integration: --check mode fails fast when manifests are out of sync, ensuring pre-commit and release-plz workflows catch stale versions before merge

Integration points:

• release-plz.toml: runs cargo xtask bindings --base-ref origin/main after bumping the root crate, so binding versions are updated atomically during the release process
• scripts/pre-commit: invokes cargo xtask bindings --check to block commits that would leave bindings out of sync
• .cargo/config.toml: defines cargo xtask alias for convenience

Documentation includes inline examples showing how version bumps behave when bindings are ahead/behind the root, and notes that the minor field acts as the major version under SemVer 0.y.z initial development phase.

[dekomissMSFT]

[anakrish]

@dekomissMSFT Thanks for the review and approval. We may need to iterate a few times to nail this. There will likely be follow up PR once we try this out in practice.