MetadataHeader::CURRENT_VERSION was not bumpted between 2.2 and 2.3

[webmaster128]

Hey all!

We are currently experiencing segfault crashes when using modules that have been serialized to disk with Wasmer 2.2.0 and deserialized with 2.3.0. We are aware the format can change between minor and even patch versions and have a way to handle MetadataHeader::CURRENT_VERSION bumps. But it seems that MetadataHeader::CURRENT_VERSION was not changed and is still at 1.

This was discussed in https://github.com/wasmerio/wasmer/issues/2781 but I don't fully understand if and how it has been resolved. Basically from our use case the request is this: the format can change any time, no problem. But we should have a way to detect that (such as reading MetadataHeader::CURRENT_VERSION or using a different API). Then we know we have to invalidate the file system cache and everyone is happy. Invalidating the cache for every minor wasmer bump would be a huge computational burden since all the modules have to be recompiled. Would be great if we can avoid that if necessary.