build(deps): pin AISimulate release SHA for Dynamo 1.6.0

[saturley-hall]

Summary

• Pin the Rust aisimulate-core crate to AISimulate release/0.13.0 tip 968e4f822a837811d6f02af0724dacb40a8c283c using [patch.crates-io] for the post-codefreeze Dynamo 1.6.0 build.
• Set the exact Rust version requirement to =0.13.0, matching the crate version declared at that commit. Apply the same source patch to the workspace and the independent Python/KVBM binding Cargo roots, and regenerate all three lockfiles. Every other locked package record is unchanged.
• Change all three Python AISimulate requirements (package, benchmarks, and container wheel staging) to >0.13.0.dev202610060000000067,<0.14.0. This excludes the current dev build, allows the final 0.13.0 release and later compatible 0.13.x releases, and excludes 0.14.0.
• Update the existing dependency consistency checks to validate identical full-SHA patches, Git lockfile sources, matching Python ranges, and installed-version membership in the declared range.

Branched directly from Dynamo release/1.6.0 tip 16b2ae50032edbdde70a9e03a7e7056fac3b7c7d. Release 1.5.0 dependency-bump precedent: #15027. This PR uses the requested Cargo source patch rather than waiting for crates.io publication.

Validation

• Dependency consistency/namespace source tests: 6 passed, 2 deselected (installed-wheel checks require the matching release environment).
• cargo update -p aisimulate-core for each Cargo root successfully resolves version 0.13.0 from the exact Git SHA.
• cargo metadata --locked --offline --no-deps --format-version 1 for the workspace, Python bindings, and KVBM bindings.
• Parsed all three lockfiles and verified that every package record other than aisimulate-core is unchanged from the release branch tip.
• Repository-pinned Black 23.1.0 and Ruff 0.5.2 checks; git diff --check.

No GPU runtime or full container build was run locally.