Better tracking of the issue.

Use gitlab environment to keep track of doc building on the gitlab side.
Allow for staging on the readthedocs trigger to allow devs to checkout
the docs outside of master.

Remove unused and unsafe dist rule.

Add a configure option for building docs, and create a CI job that will
always run to validate it. Note that make install-data doesn't need
source builds, so the environment can be quite small.

This patch also fixes the uncovered issues, and make doc build fail on
warnings.

Instead of tracking by hand the list of files that should pass
repoquality, just use git. This should ensure that we don't miss new
files, or forget to update the repoquality listing when new files are
added.

Quite a few changes needed.

New area allow to allocate data on cuda devices.
Allocation optionally include the ability to map
host memory on device memory. See cuda area
documentation.

Includes libtool helper to link cuda device object files
with the remaining of the library.

An additional error code has been added to aml errors for handling busy cuda devices
Also, all CI stages as been set not to run on branches name starting with wip.

Layout are a bit more complex as they contain extra arrays at the end
of the struct, so new macros are required.

Add new building block describing how data
is organized in memory.

Adapted to the new master from a patch sent by @cfoyer

    When building out of tree as the, make sure that target refer to
    relative paths.

    This commit also clean-up the usage of the flags and defines
    a per-target definition of flags (can be changed for a
    AM_CPPFLAGS if the global definition is good enough).
Signed-off-by: Clement Foyer <cfoyer@cray.com>

Also adds Clement to the authors list.

Out-of-tree builds are popular when one doesn't want to pollute the
source tree with objects. It also helps debug build setup issues.

Sometimes the CI fails on configure, make sure we capture the log file
for those cases.

We've recently received messages indicating that some compiler
environments out there would choke on some of the code. Let's try to
make the code as C99 compliant and as reliable as possible by activating
more warnings and breaking the CI on it.

autoconf macros fail on -Werror -Wall because of unused variable
warnings, so we deactivate those.

Generate the list of source files automatically, to ensure that we don't
miss something.

* events triggering a pipeline on master will create aml-latest dist release
* events on branches v.0.0.x will also trigger the pipeline and create a release archive aml-0.0.x.tar.gz
* new tags will trigger the release pipeline and if tag match vx.x.x then it will create a release aml-x.x.x.tar.gz
* Whenever a branch, tag is updated and a release exists, only the link to dist archives is update. Description will remain the same, but can be updated withe the script release.sh

In order to work, the release pipeline still needs to export a RELEASE_TOKEN with rights on gitlab api.

Using the conf will allow us to make incremental adds to this list.

checkpatch is the linter from the Linux kernel. This should provide a
good amount of validation on the codestyle of the repo.

Only goes on main header and basic c file for now.

The source repo has been reorganized, but the repoquality checks were
not updated. Also make sure that style checks happen early, to fail the
CI quickly.

Force libtool to static link the PIC version of our jemalloc import into
libaml, making libaml standalone. This requires us to test some
additional libraries in our own configure (pthread, and dlopen).

This also solves the long-standing issue of `make check` only working after
`make install`, while removing our custom jemalloc from the installed
libraries.

Fixes #26.

Add parallel option to the compile step to speed things up.

Disable CI runs for refs that are work in progress.

Simple gitlab-ci config with a single step, running the full list of
configure, make, make install and make check.

No tags, no split build and test for now, as artifacts are a bit tricky
to get right.

This config should grow in the future to ensure that we run all the test
on all the platforms we want.