Add non-ERC-4337 EIP-7702 multi-manager account

[hanzel98]

Summary

• add a standalone, non-ERC-4337 EIP7702MultiManagerDeleGator with two immutable default DelegationManager contracts and optional additional approved managers
• add deterministic deployment and verification support
• add concise pre-use security guidance and focused test coverage

Security considerations

• every default or approved DelegationManager has root authority to execute arbitrary calls, self-call the account, and modify mutable approvals
• the two defaults cannot be revoked for this implementation
• unknown, unofficial, unaudited, compromised, or upgradeable DelegationManager contracts can compromise the account and must be carefully verified and trusted
• mutable approvals persist when returning to the same implementation; there is no on-chain enumeration or revoke-all operation

Validation

• targeted suite: 22 passed, 0 failed, including 512 fuzz runs
• full non-RPC suite: 1,047 passed, 0 failed across 59 suites
• scoped account coverage: 115/115 lines, 36/38 branches, 27/27 functions
• forge fmt --check and forge build --sizes passed
• runtime size: 8,673 bytes; initcode: 9,110 bytes

---

Note

^{Cursor Bugbot is generating a summary for commit 51fd2d9. Configure here.}

[hanzel98]

I think we may be able to remove the relay functions:

disableDelegation, enableDelegation, approveDelegationManager, revokeDelegationManager, redeemDelegations, and isDelegationDisabled.

The user can already use execute to call any Delegation Manager that is not whitelisted, just as they would call any other contract.

The main reason to keep these functions would be backward compatibility with previous Gator accounts. However, since the function signatures have already changed, that compatibility is already broken.

Do you see any reason to keep them, @McOso?