docs: add README "Releasing" section for parity with Go client

Add a "Releasing" subsection to the Rust README "Versioning" section documenting the
crates.io distribution mechanism and the manually-triggered rust-publish.yml workflow,
so the Rust and Go sibling clients no longer diverge on release documentation. Record
the change in CHANGELOG [0.2.2].

Author: claude

CHANGELOG.md

@@ -31,6 +31,8 @@ No changes to the public interface; packaging metadata and a release workflow on
 - Documentation: removed dangling reference-style Markdown link brackets around
   `apify_client::models` (`docs/README.md`) and `futures_util::StreamExt` (`docs/misc.md`) so
   they render as plain inline code rather than broken links on GitHub.
+- Documentation: added a "Releasing" subsection to the README "Versioning" section describing the
+  crates.io distribution mechanism and the publish workflow, for parity with the Go sibling.
 
 ## [0.2.1] - 2026-06-19
 

README.md

@@ -113,6 +113,16 @@ println!("client {CLIENT_VERSION}, built against API spec {API_SPEC_VERSION}");
 - `CLIENT_VERSION` — semantic version of this crate.
 - `API_SPEC_VERSION` — the Apify OpenAPI spec version this client targets.
 
+### Releasing
+
+The crate is distributed on [crates.io](https://crates.io/crates/apify-client). The
+[`Publish Rust client to crates.io`](.github/workflows/rust-publish.yml) workflow is the release
+mechanism: a maintainer triggers it manually (`workflow_dispatch`), it runs the same
+fmt/clippy/build quality gate as CI, verifies packaging with `cargo publish --dry-run`, then runs
+`cargo publish`. The registry token is read only from the `CARGO_REGISTRY_TOKEN` repository secret,
+and a `dry_run` input allows a packaging-only run with no actual release. Bump `version` in
+`Cargo.toml` before releasing.
+
 ## Examples
 
 Runnable examples live in [`examples/`](examples). Each requires `APIFY_TOKEN` and can be