[DRAFT] refactor/SMA: Inheritable Account Refactor

[Zer0dot]

Motivation

This PR introduces a refactor that adds overridable functions to validation calls to make SMAs easier to develop, review, and audit, as well as to isolate the core contract from SMAs.

This way, creating an SMA with custom validation logic is as simple as inheriting from the parent modular account.

Solution

Add internal virtual functions wrapping validation module calls. These can then be overriden in an inheriting contract to implement custom validation logic, as is done with an SMA here.

This also involved a test refactor to leverage the same test suite for both the inheriting and original accounts. This uses a new environment boolean variable "SMA_TEST," which is true if the test suite should be run for the SMA.

This variable is then read in certain places where logic that is different between SMAs and the parent modular account is needed. Mainly, initializing with a validation, creating an account, or affecting the single signer validation (which is built-in for the SMA).

TODO

• Lint everything
• Evaluate if there's a better way to handle testing both implementations (other than making a script to run the test suite twice for each contract, but we could do that too!)
• Add comments and documentation where tests branch between SMA/RI
• Revisit factory, potentially split it into a separate factory for each implementation
• Handle upstream PR