Fix patch-package error during installation

[compojoom]

Fix a bug

fixes #153

Bug Report

Installing 4.0.0 was failing due to patch-package being a dev dependencies and the patches folder missing in the final pkg.

Implementation

I was thinking of adding a patch-package step to the actions workflow, but this would mean that people installing would need to extra run the step. So I decided to move patch-package to dependencies and include the patch in the dist.

This would increatese file size, but I think it is the most developer friendly solution.

Additional Context

Add any other context about the implementation here.

This PR:

• Adds details of the module to the README (items are sorted alphabetically)
• Adds addresses of the canonical deployments of the mastercopy for your module to deployments.json, along with addresses and ABI details to constants.ts. Ideally these should be deterministic deployments that can be easily replicated on other supported networks.
• Includes an audit from a reputable auditor.

[jfschwarz]

It seems like the only reason patch-package needs to be a dependency (rather than a devDependency) is that the postinstall runs on both, local dev setup install and for users installing @gnosis.pm/zodiac as a dependency.

Wondering if moving the patch-package call to the generate:types script would allow us to get rid of the extra dependency?

"generate:types": "patch-package && rm -rf src/types && typechain --target ethers-v6 --out-dir sdk/types './sdk/abi/*.json'",

[compojoom]

Looks like a good idea.
I've moved it to "generate:types".

I generated a local package with:

yarn prerelease
yarn pack

then installed the generated package and it seems to work fine.