Wasm storage via new gov proposal functionality not supported

[hyperschwartz]

Summary of Bug

When using the new gov proposal format with the v1 MsgSubmitProposal, the Wasmd msg handler uses the standard msg handling for the proposed messages. This causes all configurations to be regarded, including the config that can prevent wasm storage altogether. The way to fix this is to check if the sender of the StoreCode msg is the gov module account; if so, the configurations should not be regarded and the msg should be executed.

Version

Latest

Steps to Reproduce

1. Disable wasm storage by setting the wasm param code_upload_access.permission to Nobody.
2. Create a governance proposal to store code.
3. Let proposal pass.
4. Proposal will fail due to no permissions.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[iramiller]

Seel also #1428