Seems to work! I guess it can be done better, but for now that is OK.

This is not perfect but it works (and it is much faster).

For some reason I couldn't make `fflate-unzip` work with ESBuild, so
I've placed a copy and tweaked the exports.

This is a large build-time improvement, moreover we can get rid of a
lot of troublesome code regarding how to manage assets.

`esbuild` has proven a great tool so far.

Tested with both backends.

We still keep the CLI and the WASM backend on webpack, the idea is
to move them to esbuild in subsequent commits.

CLI should use a native Coq instead, it is super-slow.

We also disabled the `collab` and `ide-project` builds for now,
re-adding before merging hopefully.

The compatibility story with user .html pages needs to be revised,
IMHO as this is a foundation for the LSP backend this is the time to
drop support for some patterns we had in the past.

We will reuse this library from vsCode (and maybe other projects), so
it makes sense to put it in its own directory, and maybe even at some
point in npm.

Along the way, we will cleanup some unused code, and add typing info
borrowed from #275

This fixes the directory target rule problem.

Thanks to Rudi Grinberg!!

This should cleanup the root directory a bit; I've placed the cli
files inside `frontend`, but quite a few of these files should
eventually move to backend, as it seems to me that they functionality
that the "server" should provide, but we can do like this for now and
move things to `backend` as we see fit.

Will gradually move parts from the other repo, wacoq-bin, to `backend/wasm`.
This will allow some code reuse between the backends.

This seems helpful to detect some problems w.r.t. imports, etc...

This is rarely used live, and should allow us to make progress towards
the common protocol a bit more easy.

We reorganize jsCoq's source code as to be more modular, in particular
we start to place backend files under the `backend` directoy, and
frontend files under `frontend`.

Code as it now does work, note however that still quite a bit of work
is needed. In particular, the headless frontend should get its own
directory, the coq-jslib directory should go away, use more types,
etc...

Newer webpack{,-cli} support this.

In princple, should change Ronin to not rely on the literal name
of the constructor.

So that it can be `import`ed.

This requires renaming of webpack.config.js to indicate it is a
CommonJS module system.

We do some extra fixes for the webpack build to work.

Ronin-P2P with all of its dependencies is pretty large. So some Webpack
config is used to split it for lazy loading.

It has two facets already.

Completely bare-bones, no UI yet.
Required quite a lot of the usual polyfills.

As subcommand `jscoq sdk`.

Currently separate from the main cli, but for no good reason.
Should be a sub-command.

Relative to `headless.ts`.

So that we can create both jsCoq and waCoq packages.

Consolidated Webpack config in a single file, as is more common for
Webpack.
Provided npm scripts for running it as usual.

And so it begins.

What was needed in order to run unit tests in Node.js is
now located in `headless.ts`.
It is invoked via the regular CLI (bundled with Webpack).

Fixes #195.

Ported old code to TypeScript with major rearrangement.
Build based on Webpack.