Gitlab CI for Theodolite-Kotlin-Quarkus

This will add a CI pipeline for the Thedolite-Kotlin-Quarkus project.

In this Pipeline there is be a build and and a test stage. Additionally, there are 2 different deactivated code style tasks: ktlint and detekt.

This solves #125 (closed) except for the publishing artifacts task.

docs/release-process.md

@@ -11,14 +11,18 @@ This document describes how to perform a new Theodolite release.
 We assume that we are creating the release `v0.3.1`. Please make sure to adjust
 the following steps according to the release, you are actually performing.
 
-1. Create a new branch `v0.3` if it does not already exists. This branch will never
+1. Update `codemeta.json` to match the new version. In particular, make sure that `version` points to the version you are releasing and `dateModified` points to the date you are relasing this version. [CodeMeata generator](https://codemeta.github.io/codemeta-generator/) may help you in updating the file.
+
+2. Create a new branch `v0.3` if it does not already exists. This branch will never
 again be merged into master.
 
-2. Checkout the `v0.3` branch.
+3. Checkout the `v0.3` branch.
 
-3. Update all references to Theodolite Docker images to tag `v0.3.1`. These are the Kubernetes resource definitions in
+4. Update all references to Theodolite Docker images to tag `v0.3.1`. These are the Kubernetes resource definitions in
 `execution`, the references to *latest* in `run_uc.py`, the Docker Compose files in `docker-test` and the example `theodolite.yaml` job.
 
-4. Commit these changes.
+5. Commit these changes.
+
+6. Tag this commit with `v0.3.1`. The corresponding Docker images will be uploaded.
 
-5. Tag this commit with `v0.3.1`. The corresponding Docker images will be uploaded.
+7. Create *releases* for this tag in both, GitLab and GitHub.