Integrate wasmvm v1.2.0 (backport #1161)

[mergify]

This is an automatic backport of pull request #1161 done by Mergify.
Cherry-pick of 957b38e has failed:

On branch mergify/bp/develop_sdk47/pr-1161
Your branch is up to date with 'origin/develop_sdk47'.

You are currently cherry-picking commit 957b38e.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   Dockerfile
	modified:   README.md
	modified:   app/app.go
	modified:   go.mod
	modified:   go.sum
	modified:   x/wasm/client/cli/gov_tx_test.go
	new file:   x/wasm/keeper/keeper_cgo.go
	new file:   x/wasm/keeper/keeper_no_cgo.go
	modified:   x/wasm/keeper/proposal_integration_test.go
	modified:   x/wasm/keeper/query_plugins.go
	modified:   x/wasm/keeper/query_plugins_test.go
	modified:   x/wasm/keeper/recurse_test.go
	modified:   x/wasm/keeper/testdata/burner.wasm
	modified:   x/wasm/keeper/testdata/hackatom.wasm
	modified:   x/wasm/keeper/testdata/hackatom.wasm.gzip
	modified:   x/wasm/keeper/testdata/ibc_reflect.wasm
	modified:   x/wasm/keeper/testdata/ibc_reflect_send.wasm
	modified:   x/wasm/keeper/testdata/reflect.wasm
	modified:   x/wasm/keeper/testdata/staking.wasm
	modified:   x/wasm/keeper/testdata/version.txt
	modified:   x/wasm/types/errors.go
	new file:   x/wasm/types/errors_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   x/wasm/keeper/handler_plugin_encoders.go
	both modified:   x/wasm/keeper/handler_plugin_encoders_test.go
	both modified:   x/wasm/keeper/keeper.go
	both modified:   x/wasm/keeper/keeper_test.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[codecov]

Codecov Report

Merging #1175 (887f55f) into develop_sdk47 (650af69) will increase coverage by 0.29%.
The diff coverage is 85.45%.

@@                Coverage Diff                @@
##           develop_sdk47    #1175      +/-   ##
=================================================
+ Coverage          58.99%   59.28%   +0.29%     
=================================================
  Files                 52       53       +1     
  Lines               7160     7224      +64     
=================================================
+ Hits                4224     4283      +59     
- Misses              2645     2647       +2     
- Partials             291      294       +3     

Impacted Files	Coverage Δ
x/wasm/keeper/keeper.go	87.19% <ø> (+0.10%)	⬆️
x/wasm/types/errors.go	77.27% <77.27%> (+77.27%)	⬆️
x/wasm/keeper/handler_plugin_encoders.go	80.30% <78.04%> (-0.59%)	⬇️
x/wasm/keeper/keeper_cgo.go	92.30% <92.30%> (ø)
app/app.go	86.61% <100.00%> (ø)
x/wasm/keeper/query_plugins.go	82.55% <100.00%> (+0.73%)	⬆️

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
6.7% Duplication

[webmaster128]

This silently changes the backend from x/gov v1beta1 to x/gov v1. Is this safe? Can it create any undesired behaviour change for contracts designed for v1beta1? How do we know which governance module chains want to use?

My approach so far was to only support the classic v1beta1 and treat v1 as a new unsupported module. But generally I am extremely unsure about the abstraction level of those CosmWasm message types.

[alpe]

The gov v1beta impl is an adapter to v1. To be on the safe side, I had an e2e test introduced with the sdk47 develop branch to cover votes. Just noticed that they don't include weighted votes yet but classic ones

[webmaster128]

Diff LGTM. The issue around gov module support is independent of this PR and affects CosmWasm + Cosmos SDK 0.46+ more general.