Reconsider salsa recovery fn usage

#931 introduced salsa recovery fn usage. However, the implementation of fallback in Salsa uses [std::panic::catch_unwind](https://doc.rust-lang.org/std/panic/fn.catch_unwind.html), making it unworkable in WASM. This is due to the fact that WASM is in the standardization process for exceptions and also because support for WASM native exceptions on the Rust compiler side (rustc) is limited. Please refer to `References` section for more details.

NOTE: The old salsa doesn't use `resume_unwind` for the cycle recovering purpose, so it does work. But since https://github.com/salsa-rs/salsa/pull/285 introduced `resume/catch_unwind` usage for cycle recovery, the wasm tests in the current `analyzer` will also fail when the new version that includes the PR is released.

## How to fix it
Regarding this issue, the easiest approach would likely be to build a dependency graph(for types, aliases, traits, etc) for each ingot and calculate the SCC (Strongly Connected Components). However, considering the simplicity and performance of the implementation, and taking into account that Salsa internally builds a dependency graph, it would be ideal to use Salsa's recovery fallback if possible.

(TBW)

## References
[Support for native WASM exceptions](https://github.com/rust-lang/rust/pull/111322)
[Implementation status in major browsers](https://webassembly.org/roadmap/)
[Exception Handling Proposal](https://github.com/WebAssembly/exception-handling)

Start by reading the Salsa recovery-function usage introduced by #931 and the referenced catch_unwind and resume_unwind behavior. Check the analyzer's WASM tests to reproduce the failure. Done means cycle recovery works without breaking WASM compatibility, but the issue leaves the implementation approach open.

Written by the indexing model from the issue text.