chore: update declared Rust deps to latest patch versions

CHANGELOG.md

@@ -8,8 +8,14 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+### Security
+
+- Updated `anyhow` 1.0.95 → 1.0.104, clearing the [RUSTSEC-2026-0190](https://rustsec.org/advisories/RUSTSEC-2026-0190) unsoundness warning in `Error::downcast_mut` (fixed upstream in 1.0.103).
+
 ### Changed
 
+- Updated the remaining declared Rust dependencies to their latest patch releases: `pyo3` 0.27.1 → 0.27.2 (crash fix for Rust 1.92+ builds with debug assertions; no API changes), `serde` 1.0.228 → 1.0.229, and `serde_json` 1.0.145 → 1.0.151 (float formatting switched from Ryū to Żmij upstream — output can differ textually while remaining valid; the 60,800-case Cedar corpus passes unchanged). No behavior changes observed across unit, integration, corpus, or benchmark suites.
+
 - Removed the unused `cedar-policy-cli` crate dependency, present since the project's initial scaffold but never referenced from code. Drops 34 transitive crates (`clap`, `miette`'s terminal-support stack, `rustix`, …) from `Cargo.lock`, shrinking build time, audit surface, and the version-resolution coupling its exact `=X.Y.Z` pin on `cedar-policy` imposed. No functional change — `cedar-policy-formatter` (which backs `format_policies`) remains.
 - **Cedar Policy engine upgraded from v4.8.2 to [v4.12.0](https://github.com/cedar-policy/cedar/releases/tag/v4.12.0)** (Cedar language version 4.4 → 4.5, adding the extended `has` operator in JSON policies). No `cedarpy` API changes: the engine's breaking changes between 4.9 and 4.12 are confined to experimental features `cedarpy` does not enable (`pst`, `tpe`, `protobuf`, `tolerant-ast`), and the `partial-eval` surface is unchanged. Verified against the upstream v4.12.0 integration corpus (60,800 request cases), including the new JSON-policy-format and JSON-schema-format suites ([#106](https://github.com/k9securityio/cedar-py/pull/106)). Thanks [@h0rv](https://github.com/h0rv)!