ci: add version updates and publish to crates.io after releases

[egorsmkv]

Rename rust.yml to ci.yml and update path filters, including workflow files and release scripts. Preserve existing Rust check job names.

Add a manual update-version.yml workflow with patch/minor/major or explicit stable version input. It validates a strictly increasing canonical version, verifies packaging, creates a Cargo.toml version PR and explicitly dispatches ci.yml on the new branch. Cargo.lock remains untracked. The workflow does not tag or publish a release.

Add publish-crates.yml triggered by release.published for stable releases. It checks out the release tag, requires exact v and ancestry on master, runs default/std/entities tests and default/entities packaging dry runs, then publishes using crates.io Trusted Publishing. Add setup and release instructions to docs/development.md and remove stale hardcoded pending-version wording from README.

One-time setup: enable Actions-created PRs; configure the crates-io GitHub environment and a crates.io trusted publisher for owner RustedBytes, repository rustedbytes-tl, workflow publish-crates.yml, environment crates-io. No registry token secret is needed. Publish GitHub Releases manually or with credentials that trigger release workflows.

Validation:

• actionlint 1.7.12 and YAML parsing passed.
• 5 Python tests cover bump behavior, explicit versions, preservation of dependency versions/comments, invalid or decreased versions and release-tag mismatches.
• Rust tests passed: default 3 unit + 12 doc, std 86 unit + 16 doc, entities 89 unit + 16 doc.
• cargo publish --dry-run --allow-dirty passed for default and entities, including compilation of the packaged crate; no upload occurred.
• cargo fmt --check and git diff --check passed.

No crate version, tag or release was changed. Remote Actions have not yet been verified. The first release of the existing breaking changes should be 0.3.0 or later.