Allow compiling the packages with dune.

This MR adds support for the dune build system (documentation available here), so it is basically an updated version of !387 (closed) (CC @Blaisorblade).

Dune still has many rough edges for projects involving Coq (mostly, it lacks features), but it is still very useful. The main goal of this MR is to allow including stdpp in dune workspaces, which basically allow one to compile (parts of) all involved projects with a single dune build invocation, which is convenient to make changes to several packages at once without having to install the packages at the start of the dependency chain (which does not scale). Another large advantage of compiling with dune is caching, but that is more relevant if you have large projects.

What is included in this MR is:

• Compilation of the packages only (no tests).
• Compilation with dune (via make dune) as part of a new CI job.

What is not included in this MR, but could be worked on in subsequent MRs if there is interest:

• Generate the _CoqProject file depending on how the repo is being used (normal build: use current _CoqProject, dune build: use slightly different _CoqProject, dune workspace build: no _CoqProject since it can get in the way). Note that dune technically does not need a _CoqProject since editors could invoke dune coq top instead of coqtop, but they currently don't by default.
• Letting dune generate and manage (also install) the opam packages, which would require making dune a hard dependency, but would simplify the infrastructure significantly (no need for patching up _CoqProject with a script).
• Port the tests to dune cram tests, which could also simplify the infrastructure, but currently requires a slightly more verbose setup.

docs/dune.md

+Support for the dune build system
+=================================
+
+**NOTE:** in case of problem with the dune build ask @lepigre.
+
+The library can be built using dune by running `dune build`. Note that `dune`
+needs to be installed separately with `opam install dune`, as it is currently
+not part of the dependencies of the project.
+
+Useful links:
+- [dune documentation](https://dune.readthedocs.io)
+- [coq zulip channel](https://coq.zulipchat.com/#narrow/stream/240550-Dune-devs-.26-users)
+
+
+Editor support
+--------------
+
+Good dune support in editors is lacking at the moment, but there are trick you
+can play to make it work.
+
+One option is to configure your editor to invoke the `dune coq top` command
+instead of `coqtop`, but that is not easy to configure.
+
+Another option is to change the `_CoqProject` file to something like:
+```
+-Q stdpp stdpp
+-Q _build/default/stdpp stdpp
+-Q stdpp_bitvector stdpp.bitvector
+-Q _build/default/stdpp_bitvector stdpp.bitvector
+-Q stdpp_unstable stdpp.unstable
+-Q _build/default/stdpp_unstable stdpp.unstable
+```
+Note that this includes two bindings for each logical path: a binding to a
+folder in the source tree (where editors will find the `.v` files), and a
+binding to the same folder under `_build/default` (where editors will find
+the corresponding `.vo` files). Note that the binding for a source folder must
+come before the binding for the corresponding build folder, so that editors
+know to jump to source files in the source tree (and not their read-only copy
+in the build folder).
+
+If you do this, you still need to invoke `dune` manually to make sure that the
+dependencies of the file you are stepping through are up-to-date. To build a
+single file, you can do, e.g., `dune build stdpp/options.vo`. To build only
+the `stdpp` folder, you can do `dune build stdpp`.