fix(deps): update rust crate constant_time_eq to 0.4.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
constant_time_eq	dependencies	minor	0.2.4 -> 0.4.0

---

Release Notes

cesarb/constant_time_eq (constant_time_eq)

v0.4.2

Compare Source

• Refactor detection of the DIT feature on ARM. For builds without the
  "std" feature, there's now an undocumented function to force the use
  of the DIT bit.

v0.4.1

Compare Source

• Simplify code to make it easier to review.

v0.4.0

Compare Source

BREAKING CHANGE: this crate now has a "std" feature which is enabled by
default. Disable it if you need to use this crate as a no_std crate.

Previous versions of this crate protected against the optimizer doing an
early exit when the accumulator becomes non-zero (found a difference),
but not against a sufficiently smart optimizer doing an early exit when
the accumulator has all bits set (the accumulator never clears a bit, so
having all bits set means it will no longer change).

Protecting against that also prevents autovectorization, so this release
does manual vectorization to recover most of the speed lost. Where there
is enough compiler support (stable vector intrinsics), it uses a mix of
vector intrinsics and inline assembly for inputs which are a multiple of
the vector size, while for other architectures and for the remainder of
an input which is not a multiple of the vector size, it uses a generic
word-at-a-time implementation with the native word size.

Some newer implementations of the ARM architecture do not guarantee the
timing of instructions unless the DIT bit is set. Fortunately, that bit
can be set on all privilege levels; unfortunately, that bit only exists
on these newer implementations of the ARM architecture, and the flag to
detect whether it exists is not accessible on all privilege levels. How
to obtain that flag varies depending on the operating system, but Rust
has a good implementation of that on its standard library. This means
that runtime detection introduces a dependency on std (enabled by the
"std" feature, which is enabled by default); compile-time detection is
always available.

This release is a candidate for becoming the 1.0 release. In preparation
for that, it uses the 2024 edition, which enables the new resolver which
will allow future updates to the set of architectures which can use the
inline assembly implementation of optimizer_hide(), without breaking
downstream crates (for instance, s390x and arm64ec were stabilized in
Rust 1.84.0).

• Rewrite the generic implementation to process one word at a time,
  instead of byte by byte. Depending on the architecture, this means
  8 bytes or 4 bytes processed on each loop iteration.
• Use optimizer_hide() after each step, instead of just at the end.
• Since optimizer_hide() now works on words, it no longer neeeds the
  special case for byte sub-registers on x86 and x86_64.
• Manual implementation for SSE2/AVX (x86 and x86_64), using 128-bit
  vectors, processing up to 32 bytes on each loop iteration.
• Manual implementation for NEON (aarch64 only for now), also using
  128-bit vectors and processing up to 32 bytes on each loop iteration.
• On AArch64 with FEAT_DIT (like modern Apple devices), try to set the
  DIT flag to ensure data independent timing.

v0.3.1

Compare Source

• Use the portable optimizer_hide() when running under Miri.

v0.3.0

Compare Source

• Use black_box instead of volatile read when inline assembly is not
  available.
• Increase minimum Rust version to 1.66, which is when black_box was
  stabilized.

v0.2.6

Compare Source

• New tests using the count_instructions crate; no functional changes.

v0.2.5

Compare Source

• Add #[must_use] to all functions.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path mvstore/Cargo.toml --package [email protected] --precise 0.4.2
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)