feat(contracts): add deploy configs and implementation deploy logic for kroma L1 contracts

[sm-stack]

Description

This PR does 2 things

• Add deploy configs for kroma L1 contracts
• Add KromaDeployImplementation.s.sol, which is to deploy implementation contracts of kroma L1.

KromaDeployImplementation

Background

The reason why I made this contract is, to make the future upstream process as easy as possible while not breaking the compatibility with future modifications on OP Stack. The current OP Stack highly depends on 2 script files when deploying the smart contract: Deploy.s.sol and L2Genesis.s.sol. So adding kroma-specific one in that level will break the actions at devnet & testing.
For example, recently OP Stack made a breaking change on its devnet structure, which uses kurtosis instead of custom python file to initiate devnet. The optimism-package at kurtosis relies on op-deployer, and op-deployer calls Deploy.s.sol and L2Genesis.s.sol internally.

So I thought that instead of adding a separate deploy script for Kroma contracts, integrating the deployment process of Kroma specific contracts inside Deploy.s.sol and L2Genesis.s.sol is much better. Please suggest any ideas if you have!

Demonstration

The KromaDeployImplementation.s.sol contract takes the role of deploying the impl contracts, and doing the sanity checks of the deploy configs and deployment itself.

The KromaDeployImplementation contract will be initialized in Deploy.s.sol, and will be used to deploy kroma L1 contracts. There would be a function such as deployKromaImplementations(), which is similar with deployImplementations function. The full process will be like this:

1. deployKromaImplementations() function (which will be implemented in the following PR) will get the necessary constructor arguments from DeployConfig.s.sol and set it at KromaDeployImplementationsInput contract.
2. It will execute run() function at KromaDeployImplementation, which will then deploy the whole contracts and return it at the output format of KromaDeployImplementationsOutput.

Considerations

• Optimism actively uses contract interfaces, so I had to add interfaces for governance contracts & some function interfaces for L1 contracts to read immutable variables. There is a cyclic dependency issue between ValidatorManager and AssetManager, so I couldn't add a check for ValidatorManager address at assertValidAssetManager() function.
• Optimism used abi.encodeCall and <InterfaceName>.__constructor__ when deploying the impl contract, but I changed it to abi.encodeWithSelector. abi.encodeCall is a better one, since it checks the type of each variables when it is called, while abi.encodeWithSelector does not. The reason why I did like this was because ValidatorManager and AssetManager imports their own interfaces. If I add __constructor__(...) at the interface files, the contracts that imports those interfaces breaks, since there's no __constructor__ function in their contract. Maybe removing interface imports from ValidatorManager and AssetManager will work, but not sure it's a good idea.

Please lmk if you have any idea to solve those problems.

[sm-stack]

I've rebased this onto the target branch to apply the fix that removes importing interfaces at contracts (ValidatorManager, AssetManager). Also, based on that changes, I've managed to address the latter consideration, by commit d0c6c59.

+Addressed the first consideration by the following commit!

[sm-stack]

Added 5 commits, doing the following things

• Thanks to @0xbenyun, interface files are generated by cast interface or forge inspect. Updated all added interfaces at this commit.
• Removed interface imports from KromaMintableERC20 and ProxyAdmin contract, based on the interface policy of Optimism, at this commit.
• The interface check script which is executed at just build generates error both at the incomplete interface files like IL2OutputOracle, and at newly imported OZ contracts. Thus, I added them to 'excluded contracts' at the interface checking script, at this commit. Note that 3 contracts (IL2OutputOracle / ProxyAdmin / IL1CrossDomainMessenger) should be removed after resolving compile errors related to them at the tests.
• Added storage and abi files generated by just snapshots-abi-storage at this commit.

[seolaoh]

We can remove L10.

[sm-stack]

It is used at the supportInterface function below, so removing it will generate a compile error.

[kangsorang]

I think we've done enough work with Interface. Why don't we include this temporarily excluded part now?