Tgrade custom multitest

[ethanfrey]

Closes #144

Requires CosmWasm/cw-plus#456 (and pointing Cargo.toml to a release)

• Implement TgradeModule with init logic
• Support basic queries
• Support basic messages
• Basic sanity checks (as unit test)
• Add helpers to setup App
• Add helpers to call end/begin blockers
• Mock validator votes query
• Merge cw-plus PR and tag release (Expose essential multitest types CosmWasm/cw-plus#456 and Prepare release v0.10.0-soon3 CosmWasm/cw-plus#457)
• Update Cargo.toml deps to crate versions

Follow up (in #182):

• Add multitest for tgrade_valset with Promotion, EndBlock, and MintTokens
• Better unit test coverage

[ueco-jb]

I wonder if this
#[cfg(all(test, feature = "multitest"))]
wouldn't work better - those new multitest dependencies could be moved to [dev-dependencies] if so.

[ethanfrey]

Hmm... we could improve this flag (I would prefer to do in another PR so there is a much smaller diff).

If package A imports package B in test mode, are the dev-dependencies of package B included?

I understood it would use the dev-dependencies of the package being tested (A) and the normal dependencies of the other packages. Also #[cfg(test)] flag on the dependencies are exposed to the caller?

Again, I would prefer to merge and get #182 in (which uses these features from another package), then happy to review/approve a PR that does a less intrusive flagging of these deps

[hashedone]

I am pretty sure no - cfg(test) is set if and only if your crate is under test. You want those modules to be exported for testing in other modules (those are helpers for other modules, not this particular one).

[hashedone]

I really appreciate this change. Just wanted to take #88, but I was missing this. I see some todos but I guess to be implemented as follow up.

[hashedone]

I am pretty sure no - cfg(test) is set if and only if your crate is under test. You want those modules to be exported for testing in other modules (those are helpers for other modules, not this particular one).