GitLab

BSD3, as discussed.

The nix-env used for CI is being poluted by gitlab CI environ variables,
which ends up crashing argo_nodeos_config.

The real fix would be probably involve figuring out what kind of env
variable value crashes the whole thing and fixing our wrapping logic,
but at the same time, there's no reason for nix to use the CI env in the
first place.

This also resets the CI pointers to 'base'/'basic.yaml'.

Reorder the CI pipeline to style check first, so that we don't wait for
the entire integration tests before failing on code formatting.

nix-shell -A nrm for a nrm development environment.
nix-shell -A test for an versioned integration test environment.
nix-build -A <tab> to build a package from the versioned test environment.
nix-shell -A <tab> for other shell options.
nix-build -A <tab> for other build options.

the gitlab-ci.yml file now points to argotest/gitlab/basic.yml on
master.

This commits simplifies the CI setup for this repository, offloading
all complexity to the "argotest" repository.

These use libnrm/downstream-refactor and should be updated once that
branch is merged.

This commit pins the integration tests. This is done in the .integration.nix
file, which in turns uses the derivations from the 'argotest'
repository. These pin argopkgs - which itself pins nixpkgs, so
everything should be completely reproducible.

The integration target provisions the dependencies using nix-shell and
runs the basic 'hello world' container test.

Added integration tests to the `.gitlab-ci.yaml` file. These tests
run any runner tagged "integration". They depend on the 'argotest'
repository master branch being able to run the tests, which
uses 'argopkgs' repository. The runner must be Nix
enabled. This therefore currently uses a rolling release of the
integration tests.

Since our tests include checking that coolr can access the rapl
interface, we should ensure that only runners having rapl will test the
code.

No need to trigger CI for things that are not ready.

flake8 is an automatic style checker. This is very useful to ensure that
we have a consistent style as more people start contributing to the
code.

We ignore coolr for now, as it's a big offender.

Gitlab CI support, for a py.test run inside the pipenv configuration.