Draft: Automated test report propagation

Description

The required functionality should be able to:

• Be a separate stage in gitlab-ci, that will be launched only with each new TAG
• gather all test artefacts created during CI pipeline and put them into the text-report template
• finally build latex template with test artefacts into the pdf file, and store it as artefact in the main repository

Coverage and integration tests currently are storing their own artefacts, so its an easy solution just to add them into .tex file as raw content in the respective section.

For unittests I propose to capture output of unittests into the file and propagate this file to the test-report submodule. I think it will be enough to do only for the latest version of python.

Commits

• Added test-report submodule and its basic processing in CI

Related Issue

Closes #169

How Has This Been Tested?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.