chore: Update dependencies

[dknopik]

Update all dependencies.

Notably,

• The lighthouse dependencies to the current state of the anchor branch. This is includes an update to recent unstable as well as
  • Expose functions to do preliminary slashing checks lighthouse#7783 to enable QBFT value checks for attestations
  • Create network_utils crate lighthouse#7761 to decouple us from lighthouse_network
  • updating Implement selections Beacon API endpoints to support DVT middleware lighthouse#7016, which was already in anchor previously
• Alloy. This caused some changes around the creation of Providers, renaming on_* to connect_*.
• Libp2p, gossipsub and the peer store. There were some API changes with the latter.

I tried to split this up, but all above are linked: LH and alloy need to be updated together as the native library c-kzg is used by both. LH and libp2p unfortunately need to be updated together due to our use of dependency version patching for the unreleased peer store.

[diegomrsantos]

Are the code changes necessary after the update?

[mergify]

This pull request has merge conflicts. Could you please resolve them @dknopik? 🙏

[mergify]

This pull request has merge conflicts. Could you please resolve them @dknopik? 🙏

[jking-aus]

lgtm

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #452 has been dequeued. The pull request rule doesn't match anymore. The following conditions don't match anymore:

• label!=do-not-merge
• label=ready-for-merge
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • label!=do-not-merge.

You can check the last failing draft PR here: #472.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[dknopik]

Sorry, realized last second that this introduced a bug due to slightly changed semantics of the sync selection proof config. Fixed in fe8f956