chore: Bump Rust dependencies pre-26.7.0

[Techassi]

Bump Rust Dependencies for Stackable Release 26.7.0

Warning

It should be noted that this PR bumps yasna, which required a bump in the the forked p12 crate. I checked the changelog and nothing stood out. The build also succeeded.

This can be reverted if deemed too risky.

Part of stackabletech/issues#855

Note

During a Stackable release we need to update various Rust dependencies before
entering the final release period to ensure we run the latest versions of
crates. These bumps also include previously updated and released crates from
the operator-rs repository.

Tasks

• Bump Rust Dependencies, see below for more details.
• Add changelog entry stating which important crates were bumped (including the version).

Note

The bumping / updating of Rust dependencies is done in multiple steps:

1. Update the minimum Version in the root Cargo.toml manifest.
2. Run the cargo update command, which also updates the Cargo.lock file.
3. Lastly, run make regenerate-nix to update the Cargo.nix file.

Bump Rust Dependencies

• Bump stackable-operator and friends
• Bump product-config
• Bump all other dependencies

[adwk67]

LGTM, although I am getting some doc errors when I check locally. Should these be picked up by prek?

warning: unresolved link to `tls`
   --> rust/operator-binary/src/backend/mod.rs:104:49
    |
104 |     /// The TLS cert lifetime (when using the [`tls`] backend).
    |                                                 ^^^ no item named `tls` in scope
    |
    = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
    = note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default

warning: unresolved link to `Ok(Some(T))`
   --> rust/operator-binary/src/utils.rs:249:49
    |
249 |     /// Transforms this [`Result<T, E>`] into [`Ok(Some(T))`] if [`Ok`], [`Ok(None)`] if [`Err`] and
    |                                                 ^^^^^^^^^^^ no item named `Ok(Some(T))` in scope
    |
    = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`

warning: unresolved link to `Ok(None)`
   --> rust/operator-binary/src/utils.rs:249:76
    |
249 |     /// Transforms this [`Result<T, E>`] into [`Ok(Some(T))`] if [`Ok`], [`Ok(None)`] if [`Err`] and
    |                                                                            ^^^^^^^^ no item named `Ok(None)` in scope
    |
    = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`

warning: unresolved link to `Err(_)`
   --> rust/operator-binary/src/utils.rs:250:36
    |
250 |     /// `predicate` is `true` or [`Err(_)`] if [`Err`].
    |                                    ^^^^^^ no item named `Err(_)` in scope
    |
    = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`

warning: `stackable-secret-operator` (bin "stackable-secret-operator" doc) generated 4 warnings

[Techassi]

We run cargo doc --no-deps --document-private-items as part or the prek checks. What command did you use?

We should improve this command and also check with --no-default-features and --all-features.

[adwk67]

We run cargo doc --no-deps --document-private-items as part or the prek checks. What command did you use?

I ran:

RUST_TOOLCHAIN_VERSION="nightly-2026-02-24-x86_64-unknown-linux-gnu"

clear; cargo "+$RUST_TOOLCHAIN_VERSION" fmt;cargo check; cargo test; cargo clippy --all -- -D warnings; cargo doc --document-private-items

[Techassi]

Ah yeah, those are only warnings and don't result in a non-0 exit code. That is something we should change.