Enclave Release Cycle

[ctrlc03]

We need to figure out the release cycle of Enclave and the scripts/CI components needed to get that working.

For now we have agreed to use semver and keep a consistent version across npm/contracts/crates.

The testnet should be the same as mainnet - what works there is ready to work on mainnet.

New releases must maintain backward compatibility with testnet. e.g. enclave cli polls for version of contracts and loads the new engine while keeping support of current before the upgrade.

Keep using feature branches for active work -> merge into develop.

CI should do cross testing for backward compatibility.

We need:

• Script to bump version across the monorepo
• Action to publish everything - https://github.com/gnosisguild/enclave/blob/main/.github/workflows/binary-releases.yml
• Main branch to be most up to date. Devnet / testnet / mainnet branches

[ctrlc03]

fixed by. #764