Add no-hash-maps crate feature to wasmi_cli + enable by default

crates/cli/Cargo.toml

@@ -23,6 +23,10 @@ wat = "1"
 [dev-dependencies]
 assert_cmd = "2.0.7"
 
+[features]
+default = ["no-hash-maps"]
+no-hash-maps = ["wasmi/no-hash-maps"]
+
 # We need to put this [profile.release] section due to this bug in Cargo:
 # https://github.com/rust-lang/cargo/issues/8264
 # Uncomment the lines below before publishing a new `wasmi_cli` release to crates.io.

crates/collections/Cargo.toml

@@ -19,7 +19,7 @@ string-interner = { version = "0.17", default-features = false, features = ["inl
 ahash = { version = "0.8.11", default-features = false }
 
 [features]
-default = ["std"]
+default = ["std", "no-hash-maps"]
 std = ["string-interner/std"]
 # Tells the `wasmi_collections` crate to avoid using hash based maps and sets.
 # 
@@ -29,3 +29,9 @@ std = ["string-interner/std"]
 #
 # An example of such an environment is `wasm32-unknown-unknown`.
 no-hash-maps = []
+
+[package.metadata.cargo-udeps.ignore]
+normal = [
+    # The string-interner dependency is always specified even though it is unused when no-hash-maps is enabled.
+    "string-interner"
+]

crates/wasmi/Cargo.toml

@@ -40,7 +40,7 @@ anyhow = "1.0"
 criterion = { version = "0.5", default-features = false }
 
 [features]
-default = ["std"]
+default = ["std", "no-hash-maps"]
 std = [
     "wasmi_core/std",
     "wasmi_collections/std",