Feature: 4337 module v0.3.0-1

[mmv08]

This PR:

• Implements Release a new 4337 module version with updated JS tooling. #426 by releasing the code we have now under a new tag
• There were no contract changes, so the expected addresses are the same. I confirmed it by trying to deploy to a network where the contracts are already deployed:

> hardhat deploy-contracts --network "mainnet"

Nothing to compile
No need to generate any newer typings.
reusing "SafeModuleSetup" at 0x2dd68b007B46fBe91B9A7c3EDa5A7a1063cB5b47
reusing "Safe4337Module" at 0x75cf11467937ce3F2f357CE24ffc3DBF8fD5c226

[akshay-ap]

My understanding is that as the script has a bug fix, new version would be v0.3.1. Curious to know why there is v0.3.0-1 as new version instead? I couldn't find it as a convention in npm docs.

[akshay-ap]

Approved with comment.

[mmv08]

My understanding is that as the script has a bug fix, new version would be v0.3.1. Curious to know why there is v0.3.0-1 as new version instead? I couldn't find it as a convention in npm docs.

There is no bug in the script or the contracts per se. The bug is in the surrounding tooling. We had problems with NPM where it would generate a platform-specific lockfile and refuse to regenerate it on other platforms. This led the v0.3.0 to be only usable to deploy or verify contracts on the platform where the lockfile was generated, which happens to be Linux.

The version number suggestion came from Nick here