Synchronize independent Rust consumer lockfiles after Alloy upgrade #1692

Audit reference: I46

What can go wrong

The CRISP workspace and default template had independent lockfiles that still selected Alloy 1.3 while protocol crates required 1.4.1, so clean CI could not resolve or build them with --locked. The root manifest also contained an ignored workspace.msrv key, which looked authoritative but Cargo did not use.

When it happens

This appears in downstream/template CI after the main workspace dependency upgrade, before an E3 integration test can start. The ignored MSRV key can separately mislead maintainers about which compiler version is actually enforced.

What changed

The independent manifests were aligned with Alloy 1.4.1 and tracing-subscriber 0.3.20, only the affected lockfile selections were regenerated, and the ignored root workspace.msrv entry was removed.

Why the change works

Every Rust consumer now resolves the same compatible ABI and logging versions while retaining reproducible locked builds. Removing the unused MSRV declaration prevents a false policy signal; compiler policy must live in tooling Cargo actually reads.

Checks

The default support-script locked build and the CRISP wasm-target locked check pass.