Weekly cargo update

[github-actions]

Automation to keep dependencies in Cargo.lock current.

The following is the output from cargo update:

compiler & tools dependencies:
     Locking 11 packages to latest compatible versions
    Updating bitflags v2.9.0 -> v2.9.1
    Updating errno v0.3.11 -> v0.3.12
    Updating jsonpath-rust v1.0.1 -> v1.0.2
    Updating owo-colors v4.2.0 -> v4.2.1
    Updating sysinfo v0.35.0 -> v0.35.1
    Updating windows-bindgen v0.61.0 -> v0.61.1
    Updating windows-core v0.61.0 -> v0.61.1
    Updating windows-future v0.2.0 -> v0.2.1
    Updating windows-result v0.3.2 -> v0.3.3
    Updating windows-strings v0.4.0 -> v0.4.1
      Adding windows-threading v0.1.0
note: pass `--verbose` to see 35 unchanged dependencies behind latest

library dependencies:
     Locking 0 packages to latest compatible versions
note: pass `--verbose` to see 3 unchanged dependencies behind latest

rustbook dependencies:
     Locking 7 packages to latest compatible versions
    Updating bitflags v2.9.0 -> v2.9.1
    Updating cc v1.2.22 -> v1.2.23
    Updating errno v0.3.11 -> v0.3.12
    Updating tempfile v3.19.1 -> v3.20.0
    Updating windows-core v0.61.0 -> v0.61.1
    Updating windows-result v0.3.2 -> v0.3.3
    Updating windows-strings v0.4.0 -> v0.4.1

[rustbot]

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[rustbot]

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

[bors]

☔ The latest upstream changes (presumably #141232) made this pull request unmergeable. Please resolve the merge conflicts.