New Fusioin Mode: MetaMask Delegation Toolkit mode

[filmakarov]

The flow is like this:

• EOA user creates a MM deleGator smart account, or injects it's code to EOA address via ERC-7702
• Gator SA issues the delegation to some session address or account, controlled by the MEE Node. Gator owner (EOA) signs the delegation, which hash superTx hash injected
• This delegation only allows transferring assets required for the superTxn execution to the Nexus orchestrator Smart Account
• Delegate redeems the delegation, tokens are sent to the Nexus orchestrator Smart Account
• Nexus orchestrator Smart Account executes the superTxn as usual.

Current implementation expects the delegation to be restricted by the only caveat which is the exactExecution caveat, where calldata param has the superTxHash appended to it.
See https://docs.gator.metamask.io/how-to/create-delegation/restrict-delegation#exactexecution

---

PR-Codex overview

This PR introduces a new MockDelegationManager contract and enhances the delegation functionality within the project. It adds support for MM delegation signatures, modifies existing validation logic, and updates related tests to ensure functionality for the new delegation type.

Detailed summary

• Added MockDelegationManager contract with a getDomainHash function.
• Introduced SIG_TYPE_MM_DELEGATION in Constants.sol.
• Enhanced K1MeeValidator to handle MmDelegationValidatorLib.
• Updated error handling for ownership transfer in K1MeeValidator.
• Added delegation-related structs and functions in MMDelegationHelpers.sol.
• Implemented signature validation logic in MmDelegationValidatorLib.
• Updated tests to cover MM delegation scenarios in MM_DTK_Test_Fork.t.sol and K1MEEValidator_Test.t.sol.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[fichiokaku]

shouldn't the order here be:

(false, lowerBoundTimestamp, upperBoundTimestamp

?

[filmakarov]

no, it's (isValidationFailed, validUntil, validAfter)