Deployment, Ropsten and Goerli

[s994n]

Description

In this PR:

• Deploy contracts to Ropsten testnet - Deployment files (including contract addresses) can be found in the folder deployments/ropsten
• Deploy contracts to Goerli testnet - Deployment files (including contract addresses) can be found in the folder deployments/goerli
• Run basic setup on the Ropsten and Goerli deployed contracts to enable relevant permissions etc (same as previously done on Rinkeby), including adding calls to setSecreton the Whitelist Bond Depo and WethHelper contracts
• Create bonding markets for the public and whitelist bond depos, with the same market IDs as previously used for Rinkeby. Please see Slack threads here(non-whitelist bond depo market ids). and here (whitelist bond depo market ids)
  • On Goerli, following this error on Ropsten, the capacity for all bonding markets has been substantially increased to 1e40
• Generate signatures for the Ropsten and Goerli Whitelist Bond Depository and Weth Helper contracts. This is done in the same way as previously for Rinkeby (including the need for two JSON files)please also see here, but now using the relevant contract addresses for Ropsten and Goerli. The new json files are found as follows: For Ropsten: here (for use with Weth Helper) and here (for use with Whitelist Bond Depository). For Goerli: here (for use with Weth Helper) and here (for use with Whitelist Bond Depository).

Fixes #159

Tests

• [x] All tests still pass

Extra Notes

• This PR (and the deployed contracts on Ropsten and Goerli) also includes changes from #165, which adds getters for all bonding market IDs, to allow historical analysis
• The whitelist and public pre-list bond depository contracts use a Chainlink price feed address when creating markets and when bonding deposits are made. Unfortunately, Chainlink no longer supports price feeds for Ropsten, and does not have support for Goerli. Therefore, I have deployed two simple mocks (via remix) and used these while creating the bond markets on Ropsten and Goerli. These two mocks are:
  • Ropsten AggregatorMockEth. Address: 0xBcdF034cE6624A817c1BfEffBDE8691443e5fDbB
  • Ropsten AggregatorMockUSDC. Address: 0xc1656e185ED242c0aA3a20059Fcd311B0FF38D0A
  • Goerli AggregatorMockEth. Address: 0xF60AbA69463AC75231e742956F68577BFbC8B002
  • Ropsten AggregatorMockUSDC. Address: 0xd4293e0EBf6FE1Cc16F56A4707BEF2f38651d16f The (unchanging) values that are returned from these mocks are based on calls to the Chainlink price feeds for USD / ETH and USD / USDC on Rinkeby. See also /scripts/setupBonding/whitelistBondingMarkets.ts
• Deployment of the contracts to Ropsten and to Goerli was done in three groups, using the newly added deployment scripts deploy/013_deploy_group1.ts, deploy/014_deploy_group2.ts, and deploy/015_deploy_group3.ts. A description of which contracts are deployed by each group can be found within each script. By deploying contracts in groups (rather than all together), it is hoped to give a bit more control over the deployment and therefore ultimately make deploying to mainnet smoother and more controlled. Basic setup of the contracts (e.g. enabling relevant permissions on contracts etc) was subsequently done using the scripts that have been added within the folder scripts/setupGroups