- Re-enable orphan warnings that were manually disabled in many modules
- Remove non-Haskell files that were just sitting in the source tree
- Remove modules that were not called from anywhere
- Remove unused dependencies

This is not exhaustive by any means. In particular, some more weeding out
can be achieved by looking at individual functions and even branches of
functions. Weeder can help with that.

Also, tests pass now, locally

This commit moves `GargConfig` and the other config-related
data structures back into gargantext, so that they can be edited
and expanded without needing to worry about the prelude project.

This commit extends the reverse proxy for the microservices so that it
would serve a custom `/config` file which would contain the correct
baseUrl to initialise the websocket connection correctly.

Still needs to fix some hardcoded URLs. The problem with websockets is
that they use the first URL fragment to determine the documentId,
therefore we cannot proxy to `http://localhost:8009/notes/<frameId>`
because the underlying WS connection will use `noteId=notes`, which is
wrong.

This commit removes the need for a custom Opaleye fork by relying on
a newly-created `opaleye-textsearch` package following the design
outlined here:

https://github.com/tomjaguarpaw/haskell-opaleye/pull/563#issuecomment-1782794439

It's better to enumerate fields than not - easier to search later.

Also, a performance improvement for queryNgramsOccurrences (no VALUES).

This was (User, Either CorpusName, [CorpusId]) before, but the case of
UserMaster doesn't make sense with these parameters, so I rewrote the
function to accept only correct datatypes as inputs.

We had CoreNLP hardcoded, however with Spacy this resulted in
selectLems returning no entries, because the algo_id from DB didn't
match. Hence no singulars grouping.

This contains only data, removes some Database dependency in imports.

This reverts commit f4284b4e.

This paves the way to a more effective search in corpus by modifying the
internal "leaves" type of the `Query` type from a `Term` to a new type
called `QueryTerm`, which can either be an extact match or a partial
match, which can be rendered into a proper Postgres TS query via the
":*" syntax.

This commit refactors ever so slightly the '.Stem' modules to create a
unified interface; now Gargantext.Core.Text.Terms.Mono.Stem exports a
single 'stem' function which can be used with different
`StemmingAlgorithm`s, and now the other algorithms' functions have been
shielded behind internal modules.

This makes possible to see at glance which part of Garg are using which
stemming algorithm, as it wasn't always clearer before.

This also allows us to have a better control over the langugages, as not
all the stemming algorithms supports all the languages that Garg
supports.

This reverts commit efbe327f, reversing
changes made to 6d9bcd07.

We have contexts.hash_id which is enough (computed by postgres as a
trigger).

Split into Extract/Types/Utils modules.

Found some functions that are unused.

When user searched for a phrase with space inside, in database, the
'to_tsquery' function raised an sql error. One should use
'plainto_tsquery'. Also, a proper test was added.

Get rid of that TVar completely.

Related to purescript-gargantext#600