(i.e., fold_left instead of map + flatten + @)

Indeed, for graphs of 10000 nodes on the dfs, we need to operate
on list of 100 000 000 variables, which overflow the stack.

to be consistent with  the behavior of lv6 and lutin  (and work with the
lurette stdin.stdout mode), and so that lurette works with sasa !

as it is where they belong.

Indeed, during the explanations, it makes more sense to start with the state.

Doc: rework the documentation of the Algo API.

Its basename is the basename of the name of the .dot file.

Also provide a =--gen-register= option generates such a registring ml
file. --gen-register also generate a state.ml skeleton file.

The Makefile test/Makefile.inc also suppose that the types of the state
is defined in state.ml

To do that, I've reorganized the code

Test: with ocaml 4.08, it is impossible to load the same function twice.
Hence the need to define p.mli files for graphs with several nodes.

Also, track missing files and the alea-coloring exemples.

- the move_count node was wrong (missing parenthesis)
- the lemma an the theorem only holds for locally central unfait demon

Merge branch '11-add-lustre-oracles-to-all-examples-of-the-test-directory' of gricad-gitlab.univ-grenoble-alpes.fr:verimag/synchrone/sasa into 11-add-lustre-oracles-to-all-examples-of-the-test-directory

(I forgot to change it everywhere)

The generation scheme is now makes it easier to write oracles that do
not depend on the topology.  The idea is to generate an oracle
(specific to the graph) that includes a file that the user should
provide, and which ougth to define a generic oracle, i.e., depending
on m and n (process and actions numbers).

Merge branch 'master' of https://gricad-gitlab.univ-grenoble-alpes.fr/verimag/synchrone/sasa into 11-add-lustre-oracles-to-all-examples-of-the-test-directory

merge origin/3-compute-the-graph-degree-diameter-etc

nb: this demon is not fair: it is biased by the degree of nodes.

the doc generation should not be run on a docker that does not have emacs

Add the doc generation in the test to avoid such CI failueres in the future