The idea is that API.get for the HAL case will produce
a data producer which will submit a list of jobs where we will be
fetching documents incrementally.

This commit refactors the codebase such that instead of passing a
Conduit for the data fetched from the external APIs we have now a
`DataProducer` which can eventually support splitting the fetching of
data into multiple async jobs.

Dev allow for api error in flow

See merge request !440

Dev worker fixes

See merge request !447

Dev add option to notify users

See merge request !438

Keep only the roots in searchTableNgrams

See merge request !439

[query] a prefixed query like ~prefix should transform to 'prefix', not '"prefix'

See merge request !443

This prevents multiple workers getting the same job at the moment it
times out.

In particular:

* In ngrams search tests where we were comparing the total number of
  results returned, we need to account only for the roots, because the
  total number we would be returning from the pagination would be
  higher, as it would include children, in some cases;
* In the `AcyclipTableMap` generator, the roots we generate need to be
  so (i.e. `_ne_root` and `_ne_parent` must be `Nothing`).

After we rewrote `destroyForest`, it means that in normal conditions we
are going to output roots followed by their nodes (in in-order
ordering), so the test outputs need adjustments.

Destroying a forest should flatten any recursive children, or they won't
show up in the final ngrams table.

add missing module

See merge request !444

Add the ability to emit logging messages from a `DbTx` transaction

Closes #499

See merge request !436

Prevent importing ngrams which will lead to loops

See merge request !435

Added tests.

[CLI] db fix command, to fix hyperdata #630

See merge request !442

[search] small refactoring of the search API

See merge request !441

Dry run mode enabled by default

[API] version with git hash

See merge request !422

Continue with the flow and import terms.

This way, a failed API call doesn't prevent from the job to finish
gracefully.

TODO: Print a nice, formatted error

[cli] add support to spawn multiple workers of the same type

See merge request !437

Also, added Data.List.nubBy to limit to only 1 dispatched notification
per ws connection. This should fix a bug whereby a single user got
multiple notifications about the same thing.

Also, added `worker run-single-job` because the `run-single` option
was a bit confusing.