feat: update cosmwasm

[gluax]

Motivation

To update cosmwasm dependencies.

Explanation of Changes

Changes the wasmCapabilities function to return the array.
Also, band-aids #395, by just using a temporary directory for the temporary app.

We were also getting deprecation warnings for some actions that they will be dead at the end of the month so I updated all the actions I could.

Testing

Tests pass.

Related PRs and Issues

N/A

[hacheigriega]

Looks great! How come contracts don't have to be upgraded, though? What's the point of migration instructions like this then? https://github.com/CosmWasm/cosmwasm/blob/v2.0.0/MIGRATING.md

[gluax]

Looks great! How come contracts don't have to be upgraded, though? What's the point of migration instructions like this then? https://github.com/CosmWasm/cosmwasm/blob/v2.0.0/MIGRATING.md

I believe it's because you can specify wasmCapabilities to still have support for 1.x versions. Not sure if it's entirely backwards compatible, or if it does some other black magic.

However, the migration guide in the cosmwasm rust SDK made no breaking changes. Just interface changes. Like no longer being able to construct a type directly but using methods to create an instance.

[Thomasvdam]

Is it a problem that the simulation fails with the VM lockfile error?

panic: Could not lock exclusive.lock. Is a different VM running in the same directory already? [recovered]
	panic: Could not lock exclusive.lock. Is a different VM running in the same directory already?

[gluax]

Is it a problem that the simulation fails with the VM lockfile error?

panic: Could not lock exclusive.lock. Is a different VM running in the same directory already? [recovered]
	panic: Could not lock exclusive.lock. Is a different VM running in the same directory already?

Ah, yea, this is fixable. The recommended way from the cosmwasm team is to use a tempdir for every instance of the VM in testing. I'll take a look at that today.