Delete the component-async fuzzer (#13223)

This fuzzer was added in #12119 with the hope of being a strong vector
of fuzzing the component-model-async implementation. In the interim,
however, we've discovered:

* This fuzzer has found no issues.
* Issues like #13196 have happened, but they're bugs in `wit-bindgen`,
  not Wasmtime.
* Many issues have been discovered which this fuzzer did not uncover.
* This fuzzer takes a long time and special care to run due to needing
  to compile a large module at startup.

Overall it just doesn't seem like this is pulling its weight. Designing
a full fuzzer for component-async work I feel would need to start from
scratch. I don't actually know how to build a fuzzer to discover the
latent issues we've found via review/testing myself, but I'm hopeful
someone in the future can be more clever than I.

Closes #13196

Co-authored-by: Hyunbin Kim <akim9905@gmail.com>

Author: alexcrichton

Cargo.lock

@@ -33,16 +33,12 @@ wasmtime-core = { workspace = true, features = ['backtrace', 'serde'] }
 wasm-encoder = { workspace = true }
 wasm-smith = { workspace = true, features = ['serde'] }
 wasm-mutate = { workspace = true }
-wasm-compose = { workspace = true }
 wasm-spec-interpreter = { path = "./wasm-spec-interpreter", optional = true }
 wasmi = { version = "1.0.8", default-features = false, features = ["std", "simd"] }
-futures = { workspace = true, features = ['async-await'] }
+futures = { workspace = true }
 wasmtime-test-util = { workspace = true, features = ['wast', 'component-fuzz', 'component'] }
 serde_json = { workspace = true }
 serde = { workspace = true }
-test-programs-artifacts = { workspace = true }
-wasmtime-wasi = { workspace = true }
-indexmap = { workspace = true }
 
 [dependencies.wasmtime-cli-flags]
 workspace = true

crates/fuzzing/Cargo.toml

@@ -11,7 +11,6 @@
 pub mod api;
 mod async_config;
 mod codegen_settings;
-pub mod component_async;
 mod config;
 pub mod exception_ops;
 pub mod gc_ops;