[EXPERIMENTAL] [DO NOT MERGE] chore: ID-3927: ERC 7579 compliance adopting from Rhinestone's version of Nexus smart account

[naveen-imtb]

This version of the Passport Wallet Smart Account upgrade adopts code heavily from Rhinestone's Nexus smart account implementation.

I've stripped out some items that I've deemed unnecessary for this initial PoC like UUPSUpgradeable, ComposableExecution etc.

Pre-work:

• Bumped Solidity version to 0.8.27 here and evm_version (in this PR) to cancun to comply with the requirements of newly added project dependencies - e.g solady.

Key objectives:

• Implement function executeFromExecutor(bytes32 mode, bytes calldata executionCalldata) external returns (bytes[] memory returnData); - this is implemented in MainModuleDynamicAuthV2.sol
• Implement custom signature validation logic where we first check for an installed validator module and fallback to the existing signature validation logic - this is implemented in MainModuleDynamicAuthV2.sol

[zeroknots]

but msg.sender in this case is the contract that's trying to validate the signature right? this does work for our intentexecutor, but in the case of a permit2 transfer or compact claim. _shouldUseERC7579Validation() returns false. so you lose single singature flows. target/preclaimops (executions) need to be signed differently than the permit2 / compact EIP712.

I would stick to the proposed solution in the call where you check against installed 7579 validators via the sig = abi.encodePacked(validatorModule, sig).
that's how much 7579 accounts do it.

[naveen-imtb]

I've had to make a small change to your suggestion because there is no valid DEFAULT_VALIDATOR in the current setup and its hard coded to be the zero address.