Cargo update without rust_eth_kzg

[michaelsproul]

Proposed Changes

Update cargo dependencies while keeping rust_eth_kzg pinned to 0.5.1 due to the regression described in:

• Pin rust_eth_kzg to 0.5.1 #6608

The changes from that PR were not sufficient to actually pin the dependencies of rust_eth_kzg, because the dependencies from the workspace Cargo.toml file were not being used anywhere. To fix this, I've added them as explicit dependencies in crypto/kzg/Cargo.toml. With this change, cargo update no longer tries to update them.

Additional Info

Replaces:

• Cargo update - Mainly for discv5 update #6834

Hopefully cargo udeps doesn't fire due to these deps not being used directly 🙏 . From memory I think this case should be fine.

[michaelsproul]

Ok, this will need the MSRV bump. This is a bit naughty, because the alloy deps shouldn't be bumping MSRV on patch releases.

[michaelsproul]

MSRV bump is fine, but I've asked about Alloy's policy here just so we know how to handle this going forward:

• chore: bump MSRV to 1.81 alloy-rs/core#790

[jimmygchen]

I think we can also bump the version in lcli too?

lighthouse/lcli/Dockerfile

Line 4 in 96b00ef

FROM rust:1.80.0-bullseye AS builder

[michaelsproul]

Good catch! I thought of this and then forgot to do it 🤦‍♂️

[jimmygchen]

Looks good to me! Just added a minor comment to update lcli Dockerfile as well.

Marking this as backwards-incompat due to MSRV update.

[michaelsproul]

Updated!

[jimmygchen]

LGTM