Supporting genesis inbox contract as a first step

[blockchaindevsh]

Previously I submitted a proposal for inbox contract here, it turns out the diff will be too big for FP if we want to support dynamic updates.

Instead I think we can support genesis inbox contract as a first step, which only requires minimal changes:

1. The BatchInboxAddress can now be set to either an Externally Owned Account (EOA) or a smart contract. When a contract is used, it assumes responsibility for verifying and enforcing batch submission conditions.
2. Modification of the op-node derivation process: The op-node will be updated to exclude failed batch transactions during the derivation process. This change ensures that only successfully executed batch transactions are processed and included in the derived state.
3. Modification of the op-batcher submission process: The op-batcher will be updated to call recordFailedTx for failed batch transactions. This modification ensures that the data contained in failed transactions will be resubmitted automatically.
   1. Most failures will be detected during the EstimateGas call. However, under certain race conditions, failures may occur after the transaction has been included in a block.

(extracted from the original proposal)

We've deployed the genesis inbox contract feature and tested sufficiently in our devnet/testnet .

This approach seems to align with the current practices of other rollups. We could defer implementation of dynamic inbox contracts to future updates.