Developers should decide which interface to use, as they'll be calling the methods on the account
The protocol is considered to be account-agnostic, as long as the account implements the methods required by the specification (to be defined later), so the API may differ across accounts
This PR addresses the problem discovered in https://github.com/safe-global/safe-core-protocol/pull/99
The motivation behind these changes: