Wasm cache causes errors on upgrade

[the-frey]

This maybe is an issue that should be on wasmvm, so apologies if this is the wrong place.

We hit the same issue on Juno's uni testnet as we did back in Feb - @webmaster128 may recall :)

TL;DR moving to wasmvm 1.1 caused errors when cached code was executed, so we had to remove cache (i.e. rm -r $HOME/.juno/data/wasm/cache/modules/v3-wasmer1)

Was asked to make an issue so that it's documented.

[webmaster128]

Thanks a lot for debugging and reporting. Seems like the Wasmer 2.2 -> 2.3 upgrade was able to bypass our module version detection and silently change module serialization.

Removing the folder is a safe workaround 👍

We should now bump MODULE_SERIALIZATION_VERSION to prevent others from running into the same problem.

[webmaster128]

I took the liberty to call this a Wasmer bug (wasmerio/wasmer#3193). Not sure if it is one though. Maybe we are just looking for a guarantee Wasmer does not want to give us.