feat: Introduce web bindings and orb NPM package

[cdata]

This change proposes a milestone feature for Noosphere: a working NPM package that vends a TypeScript-based library that exposes Noosphere to JavaScript via a Wasm kernel.

In addition to the NPM package, this change includes wasm-bindgen-based FFI on the Rust side and a minimum viable Lit + Redux viewer application that is designed to render sphere content when loaded from a commodity IPFS Kubo gateway.

In support of the loading-out-of-a-gateway use case, the change includes a feature-gated KuboStorage implementation that can wrap any Storage implementation. KuboStorage will "fall back" to looking for blocks from an IPFS gateway if a requested block is not found in local storage. This makes KuboStorage suitable for read-only Noosphere use cases where an IPFS gateway API may be available.

I chose https://github.com/google/wireit to orchestrate builds across Rust and TypeScript packages. Largely thanks to Wireit, we don't need to be aware of yet-another-tool to run correct builds that span multiple source trees. Running npm run build from the typescript folder is sufficient to build everything (including Rust dependencies) in the intended order. The same goes for running tests: npm run test from the typescript folder will ensure all dependencies are built in time for the tests to run.

@aomarks has offered to lend us his scrutiny to make sure we get the most out of wireit.

Our test suite has also been expanded to include TypeScript tests (which are Mocha-formatted tests that run in headless Chrome). This should get us coverage from the JavaScript side of the web FFI.

Fixes #165

[aomarks]

🎉🎉🎉

Awesome!

Many of these suggestions are optional, in particular the ones around including files and output, because it is valid to not include those, but without them you won't take full advantage of incremental build/caching.

[jsantell]

Just looking through the Rust parts, it's looking excellent

[cdata]

I'm going to go ahead and merge since the last approval was dismissed by an unambiguously good (and small) patch. Thanks so much for the feedback @jsantell @aomarks and @SebastianZimmer !