minimal changes for working cannon on settlement main branch

[kaze-cow]

Description

In order to improve multi-network multi-repository deployments of CoW protocol, we are switching to using Cannon. This retains the existing deployment system. Unfortunately, many of the smart contracts have been updated (causing changes in the deployed contract address of the settlement contract), so techincally these also have to be referted in order for the correct package version to be generated.

Considering the smart contract changes we ultimately want to have in the next settlement contract, it seems smart to move them into a new dev branch which we use as the branch where PRs get merged until we are ready to deploy settlement v1.5

It also includes all the appropriate documentation for continued maintenance and usage of cannon.

Test Plan

Similar to other cannon releases:

• Install dependencies (yarn install)
• Run cannon package build (yarn hardhat cannon:build --network cannon --wipe)
• Verify running yarn record-cannon results in no substantial changes to the recorded package manifest (some changes are to be expected, such as timestamp and chainDumps will change due to the time changing)
• verify tests and etc. in the repo are still working as before

Related Issues

#255 -- previous PR which also removes hardhat-deploy and has much, much more changes. This PR is much more minimal.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	hardhat-cannon@​2.26.0-alpha.0

View full report

[kaze-cow]

closed in favor of #257