update to latest Wasmtime 37 and WASIp3 snapshots

Signed-off-by: Joel Dice <[email protected]>

Author: dicej

Cargo.lock

@@ -35,7 +35,7 @@ const WASI_HTTP_EXPORT_2023_11_10: &str = "wasi:http/[email protected]
 /// The `incoming-handler` export prefix for all `wasi:http` 0.2 versions
 const WASI_HTTP_EXPORT_0_2_PREFIX: &str = "wasi:http/[email protected]";
 /// The `handler` export `wasi:http` version 0.3.0-rc-2025-08-15
-const WASI_HTTP_EXPORT_0_3_0_RC_2025_08_15: &str = "wasi:http/[email protected]08-15";
+const WASI_HTTP_EXPORT_0_3_0_RC_2025_09_16: &str = "wasi:http/[email protected]09-16";
 /// The `inbound-http` export for `fermyon:spin`
 const SPIN_HTTP_EXPORT: &str = "fermyon:spin/inbound-http";
 
@@ -70,7 +70,7 @@ impl HandlerType {
                     `{WASI_HTTP_EXPORT_2023_10_18}`, \
                     `{WASI_HTTP_EXPORT_2023_11_10}`, \
                     `{WASI_HTTP_EXPORT_0_2_PREFIX}.*`, \
-                    `{WASI_HTTP_EXPORT_0_3_0_RC_2025_08_15}`, \
+                    `{WASI_HTTP_EXPORT_0_3_0_RC_2025_09_16}`, \
                      or `{SPIN_HTTP_EXPORT}` but it exported none of those. \
                      This may mean the component handles a different trigger, or that its `wasi:http` export is newer then those supported by Spin. \
                      If you're sure this is an HTTP module, check if a Spin upgrade is available: this may handle the newer version."