feat(contracts): add Kroma-specific contracts

[sm-stack]

Description

Adding kroma-specific contracts, including L1, governance, universal, and libraries.

I moved kroma-specific constants and types into separate Solidity files(KromaConstants.sol, KromaTypes.sol), for future upstream convenience. Regarding the predeploy (Predeploys.sol), I should put kroma-specific ones inside the existing OP ones, since the library file will be used in the deployment process.

Also added OZ upgradeable library with version of 4.9.3 as dependency, since there were some compile errors that some kroma-specific files that imports OZ upgradeable contract induced. The current OP Stack uses version of 4.7.3.

Expected L1 Contract Upgrades

This change may induce upgrade of the following L1 contracts. The upgrade will make those contracts to be same with OP.

• L1CrossDomainMessenger
• L1StandardBridge
• L1ERC721Bridge
• SystemConfig

In terms of KromaPortal, it seems that we can upgrade it to OptimismPortal, but needs more investigation about the effects of that change, so I decided to move KromaPortal temporarily this time.

Expected L1 Contract Upgrades (Kroma-specific)

The following contracts should be upgraded, due to the removal of Validator System V1.

• KromaPortal
• Colosseum
• L2OutputOracle
• ValidatorManager
• ZKProofVerifier

Notes on Formatting & Compile

To format the Solidity files, I used forge fmt <filename>, which seems to be used in OP Stack. Note that just executing forge fmt will change the format of some unrelated Solidity files, since the formatting is not consistent within this repository by default (be cautious).

Also did some changes on formats at the comments inside the files.

To build / compile the whole contract, please use just forge-build-dev instead of just forge-build. If the LITE mode of Foundry is not turned on, it will take about 6 minutes to compile the whole Solidity files (Note that vanilla OP Stack takes about 4-5 minutes for the compile of Solidity files).

[seolaoh]

• L1CrossDomainMessenger.sol: IOptimismPortal should be replaced with KromaPortal.
• L1ERC721Bridge.sol: since we use another address for L2_ERC721_BRIDGE, we should handle it in Predeploys.sol.
• We need to add SuperchainConfig contract in our L1 deploy process, since it is used in L1CrossDomainMessenger, L1ERC721Bridge, ...
• SystemConfig.sol
  • I wonder if it's ok to override validatorRewardScalar slot with eip1559Denominator.
  • We need to replace IOptimismPortal with KromaPortal and handle _setGasPayingToken function which uses IOptimismPortal.setGasPayingToken().
  • Probably we need to deploy GasPayingToken also.

[seolaoh]

• CrossDomainMessenger.sol: now it inherits different contracts so we need to check the backward compatibility for the storage variables. I think we need to modify CrossDomainMessengerLegacySpacer0, CrossDomainMessengerLegacySpacer1.
• ProxyAdmin.sol: We cannot upgrade our ProxyAdmin contract on L1, and there are some legacy stuffs of OP's ProxyAdmin so I think we should replace it with Kroma's ProxyAdmin contract.
• StandardBridge.sol
  • it now adds 2 slots in front of deposits. I think we need to handle it?
  • To be backward compatible, we need to add the supports for KromaMintableERC20. Esp the governance token is not upgradeable anymore, we should support the interface also.

[sm-stack]

• Probably we need to deploy GasPayingToken also.

I think if we don't use custom gas token feature, we don't have to deploy it.

[seolaoh]

• Probably we need to deploy GasPayingToken also.

I think if we don't use custom gas token feature, we don't have to deploy it.

But there are some usages of GasPayingToken in SystemConfig contract, so if we won't deploy it, then we should comment the related parts I think?

OP uses version 2.2.0 for their mainnet which does not include GasPayingToken stuffs.

[sm-stack]

• ProxyAdmin.sol: We cannot upgrade our ProxyAdmin contract on L1, and there are some legacy stuffs of OP's ProxyAdmin so I think we should replace it with Kroma's ProxyAdmin contract.

I didn't handle the ProxyAdmin part yet in the first PR review, since it seems that we have an option to use a new ProxyAdmin at the same address as OP.

[seolaoh]

Please apply forge fmt right before merging this branch since there are some changes when running forge fmt.

[sm-stack]

Also note that Optimism just removed the L2OutputOracle / OptimismPortal and all related deploy/test codes from its monorepo recently in this and this PR. So maybe at the following PR, I think removing the whole OptimismPortal.t.sol file would make us more convenient, since we have to revise various compile errors regarding fixed L2OutputOracle there.

[sm-stack]

I added a work related to removing the restriction for MPT first output index, since it would be useless after the MPT migration.

[seolaoh]

LGTM