chore(hardforks): Code Hash Assertions

[refcell]

Description

Crate: kona-hardforks in crates/protocol/hardforks/

Overview

In golandia, code hashes for network upgrade transaction contract deployments are validated using hardcoded values.

Kona currently does not test code hashes, but should still be able to assert that the codehash for the deployed contracts is correct. Since code hashes are statically defined in the OP Stack specs, kona should just use those values to assert correctness. (we can just hardcode these into tests like the monorepo does).

Output

There are a few hardfork locations where code hashes should be validated.

Ecotone

• L1Block Deployment (OP Stack Specs Code Hash value here).
• GasPriceOracle Deployment (OP Stack Specs Code Hash value here).

Fjord

• GasPriceOracle Deployment (OP Stack Specs Code Hash value here).

Isthmus

• L1Block Deployment (OP Stack Specs Code Hash value here).
• GasPriceOracle Deployment (OP Stack Specs Code Hash value here).
• OperatorFeeVault Deployment (OP Stack Specs Code Hash value here).

Resources

Optimism Monorepo code hash validation

[varun-doshi]

I'd like to take this one