build(deps): bump cmov from 0.5.3 to 0.5.4

[dependabot]

Bumps cmov from 0.5.3 to 0.5.4.

Commits

• 5c7e4f9 cmov v0.5.4 (#1485)
• 87cadbc cmov: fix clippy (#1484)
• 85600e9 rustfmt
• dba6c35 Merge commit from fork
• dad5e3b block-buffer: pin to zeroize v1.8 (#1483)
• 66cb272 ctutils: bump subtle version requirement to v2.6 (#1482)
• 34881f2 build(deps): bump hybrid-array from 0.4.11 to 0.4.12 (#1480)
• c211865 Update crates table (#1479)
• 9c8674f sponge-cursor: initial implementation (#1477)
• a00167a ctutils: fixup homepage url (#1478)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[sanity]

Closing: This bump changes the compiled WASM of a deployed contract/delegate, which changes its key and orphans existing users' data unless a migration ships. It needs to be done deliberately via the app's migration process (see freenet-app-migration), not as an automated dependency bump. The repo's own key/WASM stability check (or the absence of one for the compiled dependency tree) means this cannot be merged automatically.

[AI-assisted - Claude]

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.