feat(wasmtime-cli): enable async CM feature

[rvolosatovs]

With this I was able to run:

mod bindings {
    wit_bindgen::generate!({
        world: "wasi:cli/command",
        async: {
            exports: [
                "wasi:cli/run@0.3.0#run",
            ],
        },
        generate_all,
    });

    use super::Component;

    export!(Component);
}

use bindings::wit_stream;
use futures::SinkExt as _;

struct Component;

impl bindings::exports::wasi::cli::run::Guest for Component {
    async fn run() -> Result<(), ()> {
        let (mut tx, rx) = wit_stream::new();
        bindings::wasi::cli::stdout::set_stdout(rx);
        tx.send(b"hello".into())
            .await
            .expect("failed to write to STDOUT");
        Ok(())
    }
}

built via:

$ cargo build --target wasm32-unknown-unknown --release
$ wasm-tools component new --skip-validation  ./target/wasm32-unknown-unknown/release/p3_cli.wasm -o component.wasm

Using the wasmtime binary built from this commit

[rvolosatovs]

looks like it's mutually exclusive with module support :/

[rvolosatovs]

It appears that the error originates here

wasip3-prototyping/crates/wasmtime/src/engine/serialization.rs

Lines 575 to 579 in e510b3f

	Self::check_bool(
	component_model_async,
	other.contains(F::CM_ASYNC),
	"WebAssembly component model support for async lifts/lowers, futures, streams, and errors",
	)?;

. Interestingly, "just" enabling async for wasmtime serve works fine, as was done in #58