Send encoded Safe operation bytes to checkSignatures call

[nlordell]

Fixes #160

This PR fixes the checkSignatures call to the Safe to include both the Safe operation hash for recovery, but also the encoded operation bytes, which is required when using an ERC-1271 signer. In order to test this, the SafeMock now requires that dataHash == keccak256(data) and I added a unit test using a nested Safe set (note that this would require a staked paymaster to work with 4337 bundlers, but the test does check that the contract signatures works as expected).

[coveralls]

Pull Request Test Coverage Report for Build 6955856472

• 5 of 5 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 6901823068:	0.0%
Covered Lines:	29
Relevant Lines:	29

---

💛 - Coveralls

[mmv08]

is that because the signer would access its storage and that goes against the rules?

[mmv08]

Have just seen the public data commit. I think it's fine to leave it as internal, because it can be computed offchain

[nlordell]

I think it's fine to leave it as internal, because it can be computed offchain

Reverted. I was unsure about the change - but decided to propose it anyway just in case. The rationale was that it would be useful for computing SafeMessage hashes (where the bytes preimage is used instead of the bytes32 value).

[mmv08]

I think it's fine to leave it as internal, because it can be computed offchain

Reverted. I was unsure about the change - but decided to propose it anyway just in case. The rationale was that it would be useful for computing SafeMessage hashes (where the bytes preimage is used instead of the bytes32 value).

cant wait for 1.5.0 to get released 😄