[Bug] Upgrade c-kzg dependency to 2.0

[tarassh]

Component

consensus, eips, genesis

What version of Alloy are you on?

No response

Operating System

None

Describe the bug

I can't use latest c-kzg library with alloy library.

error: failed to select a version for `c-kzg`.
    ... required by package `alloy-consensus v0.7.0`
    ... which satisfies dependency `alloy-consensus = "^0.7"` of package `alloy-network v0.7.0`
    ... which satisfies dependency `alloy-network = "^0.7"` of package `alloy-contract v0.7.0`
    ... which satisfies dependency `alloy-contract = "^0.7"` of package `eventlogger v0.1.0 (/Users/redacted/eventlogger)`
versions that meet the requirements `^1.0` are: 1.0.3, 1.0.2, 1.0.0

the package `c-kzg` links to the native library `ckzg`, but it conflicts with a previous package which links to `ckzg` as well:
package `c-kzg v2.0.0`
    ... which satisfies dependency `c-kzg = "^2.0.0"` (locked to 2.0.0) of package `apilsevice v0.1.0 (/Users/redacted/apilsevice)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the `links = "ckzg"` value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

failed to select a version for `c-kzg` which could resolve this conflict

[mattsse]

I suggest downgrading, there are no functional changes in 2.0

we will migrate to 2.0 but needs more coordination with revm

[tarassh]

EIP-7594 was not present in v1.

[mattsse]

this needs to go into revm first https://github.com/bluealloy/revm before we can also bump it here