New gitlab-ci, with 3 stages build, test and cleanning.
I assume the runner will have docker and docker-compose installed. /!\ gitlab-runner has to be a sudoer, without asking for password. /!\ The build is only the call to ./bootstrap. The tests are done with pylint3 (can fail) and the 'test' (for unit and functionnal tests). And to terminate, cleanning is always done. This is required because otherwise bootstrap will try to erase previous data without being sudoer, and this will fail. Also to reduce the creation of files created by "root", we do not generate python cache files for the controller.