feat: Add wasm support

[dariusc93]

Previously, there were wasm support at the interface level, which also exported out to javascript as well, though this increased some complexity. However, the wasm research and implementation was postponed due to a different focus. Currently, if we are to implement wasm, we should make sure that dependencies do support wasm, split/gate off any file IO and native logic (eg reading/writing files, blocking tasks, etc) and enable the appropriate features where needed for wasm support.

Note:

• This is blocked until rust-ipfs has wasm support for warp-ipfs
  • There is basic wasm support in rust-ipfs to attempt a PoC, however more changes will be needed upstream and there may be bugs.
• Not all browsers support wasm or may have different requirements towards specific API so this may need to be taken into account.
• This does not require any exporting to javascript to prevent/reduce complexity but instead focuses on the use of rust and allow those who uses the API to make their own wrappers or exportation to javascript according to their use-case.

[dariusc93]

A couple of things to note:

• in-memory store is only supported at this time with the backend for wasm being indexeddb.
• When targeting wasm, we lose out on the ability to listen on a specific address since we are not able to listen to addresses and ports from the browser (though in the far future there may be browser-to-browser with webrtc)
• We lose transports for tcp, quic, and would rely on webrtc and websocket transports, in which case may require using a relay to connect to other peers.
  • It is advised to use native implementation for mobile and desktop while for web will fall back to those transports
• Performance may vary and may not be up to par compared to native implementation

[dariusc93]

Notes for Constellation:

• We should exclude Constellation::get and Constellation::put and instead rely on supplying a stream (Constellation::put_stream or Constellation::get_stream) or a buffer (Constellation::put_buffer or Constellation::get_buffer) when coming to wasm due to being unable to pull from the filesystem directly due to the limitation (and security aspect) of the browser.
• The crate image should be tested to determine if it supports being compiled to wasm via wasm32-unknown-unknown target

[dariusc93]

Notes for MultiPass:

• A buffer or stream should be used when uploading/updating the profile picture and banner since we are unable to pull directly from the filesystem.
• The crate image should be tested to determine if it supports being compiled to wasm via wasm32-unknown-unknown target

[dariusc93]

Notes for RayGun:

• RayGun::download_stream should be used when downloading to a filesystem so the wasm implementation can handle downloading it to disk
• RayGun::attach may require that constellation is used first and attaching it based on the constellation location due to limitation. The Location may eventually support a stream handle instead for the related file so we can stream it to constellation via Constellation::put_stream.

[dariusc93]

Notes:

• May have to build with +atomics to resolve a couple of issues I've observed.

[dariusc93]

Closing since we were able to resolve this but also due to the exported api being moved to warp-wasm repo. See #603.

Regardless of the exported api, the rust api and warp-ipfs implementation does support wasm32-unknown-unknown without needing to be exported so this have been resolved on that part.