Fix error chaining and casting with `anyhow` errors in the chain (#12705)

* Fix error chaining and casting with `anyhow` errors in the chain

Fixes https://github.com/bytecodealliance/wasmtime/issue

Fix error chaining and casting with `anyhow` errors in the chain (#12705)

* Fix error chaining and casting with `anyhow` errors in the chain

Fixes https://github.com/bytecodealliance/wasmtime/issues/12690

* add cfg that got lost

* avoid raw identifiers

* Add missing cfg for test function

show more ...

Fix using `downcast` with `anyhow::Error` (#12689)

* Fix using `downcast` with `anyhow::Error`

Previously when converting `wasmtime::Error` into `anyhow::Error` it
ended up breaking the `downcast`

Fix using `downcast` with `anyhow::Error` (#12689)

* Fix using `downcast` with `anyhow::Error`

Previously when converting `wasmtime::Error` into `anyhow::Error` it
ended up breaking the `downcast` method. This is because
`anyhow::Error::from_boxed` looks like it does not implement the
`downcast` method which is how all errors were previously converted to
`anyhow::Error`. This commit adds a new vtable method for specifically
converting to `anyhow::Error` which enables using the typed construction
methods of `anyhow` which preserves `downcast`-ness.

* Add a test showcasing anyhow-source behavior

show more ...

Fold the `wasmtime-error` crate into `wasmtime-core` (#12418)

Similar to #12398 and #12407 the idea is that all our dependency-free
(mostly) data structures and foundational data-types are in one lo

Fold the `wasmtime-error` crate into `wasmtime-core` (#12418)

Similar to #12398 and #12407 the idea is that all our dependency-free
(mostly) data structures and foundational data-types are in one location
to centralize testing, ergonomics, documentation, idioms, etc.

show more ...