chore: activate prague hardfork and Solidity version 0.8.30 as default

[zerosnacks]

Motivation

Closes: #10564

Considering 0.8.30+ ships with prague enabled we should pro-actively move to using it by default.

Solution

Adds Prague activation timestamp, fix blob_fee and blob_params to be hardfork compatible

Anvil already has prague activated per #10653

Breaking changes

Users targeting older versions (< 0.8.30) will likely experience a breaking change similar to how we've had this when we introduced cancun as a default if they don't have an evm_version specified in foundry.toml.

Follow up

• Book PR: chore: switch to evm_version prague by default book#1535
• Unblocks: chore(deps): weekly cargo update #10680
• Update: feat(forge): eip712 cheatcodes + forge cmd (eip712 + bind-json) with solar #10510 to use new normalize_evm_version_vyper helper

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

[zerosnacks]

These can be explained by differences in bytecode (like evm version) - we should make this test more robust instead of changing the address but can be done as a follow-up imo. The places where the strict assertions against the addresses are done largely make sense.

[mattsse]

smol nit

[grandizzy]

lgtm, left small nit

[grandizzy]

maybe can be simplified, or for future have a normalize_evm_version(version, language) in foundry compilers?

                        let mut evm = EvmVersion::default()
                            .normalize_version_solc(version)
                            .unwrap_or_default();
                        // Vyper does not yet support Prague, so we normalize it to Cancun.
                        if language.is_vyper() {
                            evm = normalize_evm_version_vyper(evm);
                        }
                        Some(evm)

[zerosnacks]

Good point, opened a follow-up ticket for me here: foundry-rs/compilers#278

We should either upstream this Vyper exception as is or create a unified helper as proposed

resolved