Security Tools Release (main)

Refresh arch-security-suite's lockfile after anti-evil-maid gained libc

The suite depends on the five other crates by path, so adding libc to
anti-evil-maid changed the suite's dependency graph too. Its own Cargo.lock
still had the old graph, and the release workflow builds with --locked, so the
job failed with "cannot update the lock file because --locked was passed"
before it compiled a single line.

The website deploy was green on the same commits, which is why this was not
obvious: only the Rust release workflow enforces --locked.

All six lockfiles now verify under `cargo metadata --locked`.

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