In ".gitlab-ci.yml" and ".gitlab-ci-templates.yml", use "${...}" notation to expand variables instead of "$...".

Furthermore, added "manual" trigger to job template ".template_deploy_branch".

In ".gitlab-ci-templates.yml", added job template ".template_deploy_branch" which uses CI variables to create unique names and use this template in ".gitlab-ci.yml".

Refactored ".gitlab-ci.yml" completely and use templates combined with "include" and "extends" keyword.

This script was deleted in previous commit because it is not required anymory.

A new issue was created to find the core problem or to implement a
re-translation of the origin only for simulation time

Moved CI helper scripts to "Tools/ContinuousIntegration" and enabled Java assertions in POM files and helper scripts.

.gitlab-ci.yml:
- Refactored complete file: moved comment on top of file.
- Call helper scripts in "Tools/ContinuousIntegration" instead of just "Tools".

Tools/ContinuousIntegration/run_vadere_console_with_all_scenario_files.py:
- Execute scenario files alphabetically.
- Use "-enableassertions" when invoking Java.

POM files:
- Use "<enableAssertions>true</enableAssertions>" to be independent of SureFire's default settings.

.gitlab-ci.yml:
- Use "mvn <options> <phase>" syntax consequently like mentioned in "mvn --help".

Renamed "run_vadere_console_with_all_scneario_files.py" to "run_vadere_console_with_all_scenario_files.py" and call it in ".gitlab-ci.yml".

In ".gitlab-ci.yml", skip unit testings in job "run_scenario_files" because on virtual maching OpenCl tests fail.

In ".gitlab-ci.yml", added job "run_scenario_files" which is invoked during GitLab's "deploy" stage.

# Conflicts:
#	.gitlab-ci.yml