fix(forge): respect Amsterdam code size limits

[figtracer]

Summary

• derive default contract size-report limits from the active EVM specification
• use revm's protocol constants for EIP-170, EIP-3860, and Amsterdam's EIP-7954 limits
• apply the same spec-aware fallback to script deployment warnings while preserving explicit code_size_limit overrides

Motivation

Selecting evm_version = "amsterdam" still made forge build --sizes and script checks use the pre-Amsterdam 24 KiB runtime / 48 KiB initcode limits. The workaround was to set code_size_limit, but that setting also configures the test executor and can prevent oversized test contracts from deploying.

With this change, selecting Amsterdam automatically uses its 32 KiB runtime and 64 KiB initcode limits, so users do not need to change the test executor limit just to get accurate size checks.

Addresses #14761 (comment)

[mablr]

Makes sense

[sakulstra]

With this change, selecting Amsterdam automatically uses its 32 KiB runtime and 64 KiB initcode limits, so users do not need to change the test executor limit just to get accurate size checks.

Should be Raise the maximum contract code size from 24KiB to 64KiB and initcode size from 48KiB to 128KiB., no?
https://forkcast.org/eips/7954/

Thanks for patching this <3

[mablr]

@sakulstra Yes, you’re right. But the revm 41.0.0 constants used here still reflect the earlier 32/64 KiB draft values; so we'll need to bump revm.

[mablr]

Marking as "blocked" until next revm bump.

[sakulstra]

Should code_size_limit be ignored on tests/scripts anyways though?