Merge contents of rover repo into red-bank repo

[larry0x]

Commands I used to prepare this PR:

git clone https://github.com/mars-protocol/red-bank.git
git clone https://github.com/mars-protocol/rover.git
cd red-bank
git checkout -b merge
git remote add rover ../rover
git fetch rover master
git merge rover/master --allow-unrelated-histories
# have fun resolving conflicts...

I don't have a good idea how to merge the deployment scripts. For now I simply rename the files (e.g. deploy.ts in the Rover repo is now deploy.rover.ts)

[larry0x]

Getting "No space left on device" error for coverage

[markonmars]

It might be unnecessary to merge the rover and redbank deploy scripts together into one, but we could unify them somehow so that we can deploy everything with on command.

[piobab]

Getting "No space left on device" error for coverage

We have two options:

1. something similar to this Enable test coverage #305
2. bump worker disk space

We already decided to go with option 1) for red-bank so maybe we should do it for whole repo the same way, thoughts @larry0x @dancreee ?

[piobab]

PR is difficult to review :D so better to check diff between rover repo latest commit (mars-protocol/rover@1176c73) and current branch commit bebf5cc

No differences, LGTM!

[dancreee]

Getting "No space left on device" error for coverage

We have two options:

1. something similar to this Enable test coverage #305
2. bump worker disk space

We already decided to go with option 1) for red-bank so maybe we should do it for whole repo the same way, thoughts @larry0x @dancreee ?

agree if it's practical to do this

[piobab]

All tests passed for me locally, except for:

failures:
    redbank_quering_oracle_successfully
    redbank_should_fail_if_no_price

It is related to libraries feature flag enabled for params contract

thread 'redbank_should_fail_if_no_price' panicked at 'called `Result::unwrap()` on an `Err` value: ExecuteError { msg: "failed to execute message; message index: 0: Error calling the VM: Error during static Wasm validation: Wasm contract doesn't have required export: \"instantiate\". Exports required by VM: [\"allocate\", \"deallocate\", \"instantiate\"].: create wasm contract failed" }', integration-tests/tests/helpers.rs:149:69

Once we extract msgs to types we can remove feature flag and tests should pass.

Moreover we are going to solve no space error by reorganization of tests in separate PR (@larry0x pointed to https://github.com/confio/poe-contracts/tree/main/contracts/tgrade-valset/src and it could make sense).

[piobab]

@dancreee we agree with @larry0x to merge this PR and fix the rest in separate smaller PRs.