[WIP] Chore: use hardhat deploy

[fabianschu]

What's new?

• instead of using custom deploy scripts, we use hardhat-deploy:
  • there is a new folder deploy that contains the deployment scripts
  • in order to deploy to rinkeby, one would have to run npx hardhat deploy --network rinkeby, for mainnet npx hardhat deploy --network mainnet
  • more infos about the plugin here
  • additional benefit: contracts are automatically deployed before running tests
• instead of using custom scripts to interact with contracts we use hardhat tasks:
  • a task can be run via the CLI
  • check out npx hardhat to see all available tasks with their descriptions
  • if you run a task you need to specify the network where you want to run it, e.g. npx hardhat --network rinkeby changeOwner --address <some_address> runs the changeOwner task on rinkeby to change the owner address of SeedFactory
  • per default the signer is the first account (accounts[0] / root ). this can be changed.
  • more infos about tasks here
• added hardhat-deploy-ethers which gives access to the getContract method which lets you easily instantiate contracts -> Caveat is that there currently is an issue when it's used together with hardhat-waffle. So, I deleted hardhat-waffle. For that reason the tests need to be slightly adapted (see todos)

Todo:

• tasks involving gnosis api are not yet complete / working -> need to be finished
• adapt existing tests to the new deployment logic
• adapt existing tests to the missing hardhat-waffle dependency: this is easy, the following lines need to be added to the top of all spec files until there is a fix for the issue:

  const {expect, use} = require("chai");
  const {solidity} = require("ethereum-waffle");
  use(solidity);

• write new tests for tasks? dunno

closes #50

[fabianschu]

Some more infos on hardhar-deploy:
If you deploy via hardhat-deploy it generates deployment files in the deployments folder. If you later on interact with contracts, e.g. via tasks, hardhat uses these deploymemt information to interact with the correct network and addresses. You can add historical deployments manually by adding the corresponding JSON files (these contain the contracts' addresses and abis).

[fabianschu]

I miiight have become slightly obsessed with refactoring existing tests to make use of hardhat deploy scripts. However, I came to the conclusion that this is not really necessary. I wouldn't wan't to remove all commits, since at some point they could still be helpful (as inspiration), but I would like to close this branch. I created a new branch, where I went back to a previous commit (before all the refactoring). All tests are green there, but the original test-init.js script is still used. I think I would leave the tests like this for now. Please find the new branch here.