Recent inclusion of fuel-chain-config prevents WASM builds

[deekerno]

The recent inclusion of fuel-chain-config in fuels-types has led to an inability to build for the wasm32-unknown-unknown target for packages depending on said crate; this is due to mio being present in the dependency graph by way of fuel-core-interfaces and its dependence on tokio. More information can be found here: FuelLabs/fuel-indexer#423. We rely on fuels-core/fuels-types pretty heavily for our indexing functionality, so any help would be appreciated.

[Br1ght0ne]

Related work is on #429, I will attempt to decouple pieces relevant to this in a separate PR.

[Br1ght0ne]

Posting my previous comment for posterity:

• eventsource-client is not supported on WASM, as it uses hyper's tcp feature
• there is a crate called spinta which wraps eventsource-client on desktop platforms and uses web_sys::EventSource (e.g. EventSource Web API) on WASM
• the Web EventSource API supports neither POST nor JSON payloads: https://stackoverflow.com/questions/23825771/how-to-pass-post-parameters-with-html-sse/54911862#54911862

We need to either use some other protocol instead of SSE (WebSockets?) or some other JS library for WASM (sse.js?).