feat: storage mirror root registry

[0xOneTony]

🤖 Linear

Closes SAF-30, SAF-31, SAF-32

[linear]

SAF-30 StorageMirrorRootRegistry

This contract should accept and store storageRoots of the StorageMirror contract in L1.

SAF-31 StorageMirrorRootRegistry Tests & Docs

• 100% unit test
• Natspec comments

SAF-32 StorageMirrorRootRegistry Contract

• Should store an immutable address of the StorageMirror address in L1, that is needed for the verification
• Should have a mapping(L1BlockNumber => verifiedStorageRoot) verifiedStorageMirrorStorageRoots that will store all verified storage roots of L1 at a specific block.
• Has a function queryL1BlockHeader(blockNumber) that should query a magical oracle that will return the L1 Block Header at a specific block. This is gonna be used to check against the proposed root by an off chain agent.
• Has a function proposeAndVerifyStorageMirrorStorageRoot(rewardNonce, blockNumber, storageRoot, MPTproof), this function should call the queryL1StateRoot at the provided block number and then call the Verifier contract and verifyStorageMirrorStorageRoot(storageRoot, MPTproof, blockheader) to verify if the StorageMirror storageRoot is part of the state tree. If it is then save it in the verifiedStorageMirrorStorageRoots mapping. ⚠️ The payment for the verification should happen after the verification is successful but inside the Verifier module
• VerifiedStorageMirrorStorageRoot(uint256 homeChainBlockNumber, bytes32 storageRoot) will emit after a proposeAndVerifyStorageMirrorStorageRoot call

[excaliborr]

After thinking more about it, i thinks its good UX to save the block number as well so a new searcher who wasnt previously subscribed to the events knows what the latest verified block was easily, it makes the operation slightly more expensive but i think its good UX for searchers,everything else looks good.

[excaliborr]

Lgtm!