chore: repin Cargo.Bazel.json.lock

The cherry-pick of #11090 ("fix: patch pcre2-sys for reproducibility")
carried over master's `Cargo.Bazel.json.lock`, whose `checksum` is a
digest over the crate_universe config and splicing manifest — i.e. over
`bazel/rust.MODULE.bazel` plus every workspace `Cargo.toml`. Those differ
between master and this RC branch, which is 28 commits behind (master has
since moved `comparable` to the dfinity fork, added `axum-otel-metrics`,
`duration-string` and `exitcode`, bumped `canbench-rs` and `ciborium`, …),
so the digest is stale here and every Bazel invocation fails at analysis
time:

    Error: Digests do not match:
      Current  Digest("987c09bb853448361351d6b167b9e528c23cea8fdaa95ce28b65cc3a9114fbce")
      != Expected Digest("4991a9aa71efd82294bf1844c7f4e677fc0fdad5c5d280d67766a7edd824e45b")
    The current `lockfile` is out of date for 'crate_index'.

Regenerated with `./bin/bazel-pin.sh`. The resolved crate set was already
correct for this branch, so the only change is the recorded checksum,
which now matches the digest CI computes. `bazel query @crate_index//:all`
and `bazel build --nobuild //publish/canisters:bundle` pass again.

Same fix as the one applied to rc--2026-08-06_04-21-revert_dmt-fix-repro.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: pietrodimarco-dfinity

Cargo.Bazel.json.lock

@@ -1,5 +1,5 @@
 {
-  "checksum": "987c09bb853448361351d6b167b9e528c23cea8fdaa95ce28b65cc3a9114fbce",
+  "checksum": "4991a9aa71efd82294bf1844c7f4e677fc0fdad5c5d280d67766a7edd824e45b",
   "crates": {
     "actix-codec 0.5.1": {
       "name": "actix-codec",