Upgrade Wasmer to Version 3

[webmaster128]

Upgrading to Wasmer 3 is important to keep in sync with the upstream development. The following changes have been highlighted by the team:

1. We solved a lot of side effects that were indirectly causing memory leaks in some edge cases
2. It increases performance of Wasmer (since wasmer::deserialize should be now zero-copy)
3. It improves greatly the API to be more resilient long-term

One thing I noticed during the integration work was that we can now copy byte arrays in and out utilizing WasmSlice and don't have to loop over bytes anymore.

In #1438 and #1467 the integration work was started.

Before we can finalize and merge this, we need the following issues to be solved:

• Bring back module size calculation to Wasmer 3 wasmerio/wasmer#3249
• How to access the Store from an import implementation (e.g. to call set_remaining_points)?

Bonus issues to track which are important are not blocking

• Module serialization stability (i.e. write modules with Wasmer verion X and read them with Wasmer version Y) MetadataHeader::CURRENT_VERSION was not bumped between 2.2 and 2.3 wasmerio/wasmer#3193

[ethanfrey]

Happy to add to next release if wasmer is ready by then.
Otherwise, just keep on ice til wasmer issues resolved

[webmaster128]

Done in #1674