Migrate to hardhat-toolbox and Ethers.js v6

[nlordell]

Supersedes #100

This PR implements the suggestion from #100 (review) (thanks @mmv08 for the suggestion!), and migrates the 4337 package to use the latest hardhat with @nomicfoundation/hardhat-toolbox in order to simplify dependency management (it also removes a lot of extra dependencies that were pulled in by ethereal-waffle 🎉).

Note that, in order to use the latest version of hardhat and hardhat-toolbox, the codebase needed to migrate to Ethers.js v6 which caused some fairly small changes to the existing TypeScript codebase.

Some additional dependency version changes that may seem unrelated but worth clarifying:

• solc: A follow up to Feature: Adjust compiler settings and document optimizer usage #99, where the direct solc version didn't change to reflect the hardhat compiler settings
• @types/node: Updated to the LTS version of node, which we intend to use.

Additionally, for testing I was able to execute the runOp script (tx).

[coveralls]

Pull Request Test Coverage Report for Build 6613336725

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.8%) to 69.856%

---

Totals
Change from base Build 6575637387:	-0.8%
Covered Lines:	102
Relevant Lines:	129

---

💛 - Coveralls

[mmv08]

Hmm, I think the version 1.4.1 still uses ethers v5. I'm wondering if this override is safe. Or does npm not allow installing dependencies because of incompatible packages in case there's no override?

[nlordell]

Or does npm not allow installing dependencies because of incompatible packages in case there's no override?

The issue I ran into is that both @nomicfoundation/hardhat-toolbox and @safe-global/safe-contracts have an ethers peer dependency with non-overlapping version ranges. AFAICT, NPM does not support this (looked for a bit online but didn't find anything conclusive, I may be wrong though).

Furthermore, I noticed that we use @safe-global/safe-contracts only for contracts and not exported TypeScript/JavaScript code, so even if we override the ethers version, it should not cause any problems.

And finally, the other thing that I found confusing was that the package.json in the safe-contracts repo does not include an ethers dependency or peer dependency, while the one published to NPM does.

[mmv08]

And finally, the other thing that I found confusing was that the package.json in the safe-contracts repo does not include an ethers dependency or peer dependency, while the one published to NPM does.

I think it was a result of the upgrade to the hardhat-toolbox as well since ethers is already a dependency of the hardhat-toolbox package. But this upgrade happened after 1.4.1, which has not been released yet.

[mmv08]

Good job sir

[nlordell]

Thanks for your help 😄