Migrate wasi-common to `wasmtime::error` (#12293)

* Migrate wiggle and wiggle generate to `wasmtime::error`

* Fix testing `wiggle` and `wiggle-test` in isolation

When doing plain old `cargo test -

Migrate wasi-common to `wasmtime::error` (#12293)

* Migrate wiggle and wiggle generate to `wasmtime::error`

* Fix testing `wiggle` and `wiggle-test` in isolation

When doing plain old `cargo test -p wiggle` (or `wiggle-test`) the test would
fail due to linking errors because Wasmtime's `std` cargo feature (and maybe
others) wasn't being enabled. The crate's tests would pass when run as part of
the whole workspace, however, because of cargo feature resolution and other
crates that enabled the necessary features, which is why CI is green.

* Remove direct anyhow dependency in wiggle-test

* Migrate wasi-nn to `wasmtime::error`

* Migrate wasi-keyvalue to `wasmtime::error`

* Migrate wasi-io to `wasmtime::error`

* Migrate wasi-http to `wasmtime::error`

* Migrate wasi-config to `wasmtime::error`

* Migrate wasi-common to `wastime::error`

This is another interesting one because wasi-common is used internally to
Wasmtime but also by other projects. Therefore, rather than using
`wastime::error::*` and making `wasmtime` a hard dependency, we use just
`wasmtime_environ::error`.

* cargo fmt

show more ...

Remove usage of `async_trait` in `wiggle` bindings (#11839)

* Remove use of `async_trait` in `wiggle` bindings

* Remove usage of re-export for non-`wiggle` traits

* Use fully qualified name for `F

Remove usage of `async_trait` in `wiggle` bindings (#11839)

* Remove use of `async_trait` in `wiggle` bindings

* Remove usage of re-export for non-`wiggle` traits

* Use fully qualified name for `Future`

Since `Future` is not in the prelude for pre-2024 editions.

show more ...