Precompute fields in VMOffsets

This commit updates the implementation of `VMOffsets` to frontload all
checked arithmetic on construction of the `VMOffsets` which allows
eliding all checked arithmetic when accessing the fields of `VMOffsets`.
For testing and such this adds a new constructor as well from a new
`VMOffsetsFields` structure which is a clone of the old definition.

This should help speed up some profile hot spots I've been seeing where
with all the checked arithmetic on field sizes this was slowing down the
various accessors during instantiation (which uses `VMOffsets` to
initialize various fields of the `VMContext`).

crates/runtime/src/instance/allocator/pooling.rs

@@ -21,7 +21,7 @@ use std::mem;
 use std::sync::{Arc, Mutex};
 use wasmtime_environ::{
     entity::{EntitySet, PrimaryMap},
-    MemoryStyle, Module, Tunables, VMOffsets, WASM_PAGE_SIZE,
+    MemoryStyle, Module, Tunables, VMOffsets, VMOffsetsFields, WASM_PAGE_SIZE,
 };
 
 cfg_if::cfg_if! {
@@ -302,7 +302,7 @@ impl InstancePool {
         let page_size = region::page::size();
 
         // Calculate the maximum size of an Instance structure given the limits
-        let offsets = VMOffsets {
+        let offsets = VMOffsets::from(VMOffsetsFields {
             pointer_size: std::mem::size_of::<*const u8>() as u8,
             num_signature_ids: module_limits.types,
             num_imported_functions: module_limits.imported_functions,
@@ -313,7 +313,7 @@ impl InstancePool {
             num_defined_tables: module_limits.tables,
             num_defined_memories: module_limits.memories,
             num_defined_globals: module_limits.globals,
-        };
+        });
 
         let instance_size = round_up_to_pow2(
             mem::size_of::<Instance>()