Update wasmer

[chipshort]

Also had to ./devtools/update_crate.sh tracing because of some incompatibility between wasmer and the tracing version we were using before.
As well as bumping the minimum Rust version to 1.73

It seems we currently allow some simd float operations in the Gatekeeper. Those should be caught by the Validator in the ParsedWasm, but I moved them to the simd section of the Gatekeeper anyways (so they are now forbidden in the Gatekeeper too).

I'm also wondering if we could streamline the Gatekeeper changes a bit by using the wasmparser::for_each_operator! macro for matching whole proposals of operators. That would make it much easier to update in the future.

[webmaster128]

I'm also wondering if we could streamline the Gatekeeper changes a bit by using the wasmparser::for_each_operator! macro for matching whole proposals of operators. That would make it much easier to update in the future.

If it helps, sure. I don't this. I think the important thing is to ensure we do exhaustive matching.

[webmaster128]

Nice.

Rust 1.73.0 is currently the highest version we can use (see CosmWasm/wasmvm#513). But that version seems to be fine.

[webmaster128]

Diff LGTM. Could we get a CHANGELOG entry and update this comment:

/// - **v9**:<br>
///   New version because of Wasmer 4.2.2 -> 4.2.5 upgrade.
///   Module compatibility between Wasmer versions is not guaranteed.

[chipshort]

update this comment

This version number wasn't bumped because the current_wasmer_module_version increased, so the cache gets invalidated already by that

[webmaster128]

I was thinking about the comment for "v9" which becomes "Wasmer 4.2.2 -> 4.2.6 upgrade". v9 is currently not yet deployed and just the dev version on main as far as I can tell.

[chipshort]

Ah, that makes sense then. I didn't notice that v9 was not deployed yet

[webmaster128]

This change is good, but under the ## [2.0.0-rc.1] - 2023-02-09 header. Do we remove the pre-release headers when we get the full release (I perfer so)?

[chipshort]

Yes, that's what I did in the past. I think it makes the most sense since people who upgrade are probably most interested in the difference between 1.5 and 2.0.