feat(config): upgrade default evm_version to cancun

[zerosnacks]

Component

Other (please describe)

Describe the feature you would like

We should evaluate whether it already makes sense to default to either: cancun (13 Mar 2024) or shanghai (12 Apr 2023) from paris (15 Sep 2022). (source)

The current configuration is:

evm_version = "paris"

The table of https://www.evmdiff.com/features?feature=opcodes shows tstore and tload are not supported on Avalance and Linea but is available on the other rollups. The current support of the entire cancun upgrade on L2s seems largely there, other EVM compatible chains have less support.

For 1.0 I think it also makes sense to establish an expectation that the default we set trails by x months.

Additional context

Considering this is a breaking change and most users have possibly not specified an evm_version this change can introduce unintended side effects.

It may make sense to pin to paris for 1.0 and apply the breaking changes post-release.

[zerosnacks]

cc @grandizzy just noticed that Hardhat also defaults to cancun: https://hardhat.org/hardhat-network/docs/reference#hardfork

I think we can make this change without much issues