Enable the memory64 proposal by default

[alexcrichton]

The memory64 proposal for WebAssembly moved to phase 4 early last November which was the final remaining blocker for enabling it in Wasmtime. I've gone ahead and enabled it here with all the other checkboxes being ticked such as:

• Tests - all spec tests are enabled and we have a few tests here and there for memory64 behavior throughout the unit test suite.

• Finished - this proposal's memory-facing bits have been done for quite some time and the final 64-bit table bits have been done for a bit now as well.

• Fuzzed - this is enabled in wasm-smith and additionally has custom fuzzing via the memory_accesses fuzzer.

• API - all APIs related to memory work with u64 values to accommodate 64-bit memories and the 64-bit-ness is reflected in the type of memories.

• C API - the C API's functions for working with memories all reflect 64-bit indices like the Rust API.

[github-actions]

Label Messager: wasmtime:config

It looks like you are changing Wasmtime's configuration options. Make sure to
complete this check list:

• If you added a new Config method, you wrote extensive documentation for
  it.

  Details

  Our documentation should be of the following form:

  Short, simple summary sentence.
  
  More details. These details can be multiple paragraphs. There should be
  information about not just the method, but its parameters and results as
  well.
  
  Is this method fallible? If so, when can it return an error?
  
  Can this method panic? If so, when does it panic?
  
  # Example
  
  Optional example here.
  

• If you added a new Config method, or modified an existing one, you
  ensured that this configuration is exercised by the fuzz targets.

  Details

  For example, if you expose a new strategy for allocating the next instance
  slot inside the pooling allocator, you should ensure that at least one of our
  fuzz targets exercises that new strategy.

  Often, all that is required of you is to ensure that there is a knob for this
  configuration option in wasmtime_fuzzing::Config (or one
  of its nested structs).

  Rarely, this may require authoring a new fuzz target to specifically test this
  configuration. See our docs on fuzzing for more details.

• If you are enabling a configuration option by default, make sure that it
  has been fuzzed for at least two weeks before turning it on by default.

---

Details

To modify this label's message, edit the .github/label-messager/wasmtime-config.md file.

To add new label messages or remove existing label messages, edit the
.github/label-messager.json configuration file.

Learn more.

[dicej]

LGTM. Do we need to do anything special (that hasn't already been done) to indicate that memory64 is not yet compatible with components? Or will that be caught by wasmparser at validation time?

[alexcrichton]

Oh you know that's a good point. I haven't checked up on the state of memory64 and components in awhile. I know some parts support some things but not all, and I suspect that there are a number of memory64-related panics in Wasmtime which I should convert to errors first before landing this.

[alexcrichton]

On review looks like less has support for this than I thought. I've opted to go with a wasmparser validation change for now since components don't currently specify how everything works anyway.

[alexcrichton]

I'm going to flag this for merging now that wasmparser has been updated and components reject memory64-based memories explicitly.