Get our contracts deployed to Goerli for cross-chain testing

[stevieraykatz]

Ticket(s): #204

Explanation of the solution

• Create tasks necessary for deploying side-chain infrastructure (Router, registrar)
• Create/modify tasks for configuring the side-chain infra
• Create a dummy vault for purposes of testing full stack investment calls
• Deploy Router
• Deploy Registrar
• Deploy DummyVault
• Configure all the things (both primary and side-chain)

Instructions on making this work

• run yarn or yarn install to install npm dependencies
• run yarn test to verify all tests still pass

[stevieraykatz]

@misicnenad it would be great to get your eyes on this infra sooner than later.

I created a new, separate address json specifically for integrations because it will have an arbitrary length (which doesn't play nicely with the generic 'address obj` and which is also independent of chain, i.e. each named integration will have a unique set of contracts on a singular and specific chain.

It does however have a reusable structure: {strategy, locked, liquid}. As such, the manageStratParams tooling is set up to write these specific objects to the json files as strategies are deployed.

The new stratConfig.ts file is meant to be the "settable config" for each new strategy. I'm open to suggestions on how to manage this. I wanted to avoid needing file path/system scrapers for pulling configs from each respective integration folder so I opted for this more strictly typed, all-encompassing config file.

[stevieraykatz]

Last pending step is to set the Goerli network info on the primary Registrar (mumbai network).