Verification report tooling

Verification report tooling is required by
- https://eclipse-score.github.io/process_description/main/process_areas/verification/guidance/verification_process_reqs.html#gd_req__verification_reporting
- https://eclipse-score.github.io/process_description/main/process_areas/verification/guidance/verification_process_reqs.html#gd_req__verification_report_archiving
- https://eclipse-score.github.io/process_description/main/process_areas/verification/guidance/verification_process_reqs.html#gd_req__verification_checks
- https://eclipse-score.github.io/process_description/main/process_areas/verification/guidance/verification_process_reqs.html#gd_req__verification_checks_extended

This has to be implemented.

Connected with this is the topic of representation of the test cases in S-CORE:
- https://eclipse-score.github.io/process_description/main/process_areas/verification/guidance/verification_templates.html#gd_temp__verification_specification defines how the documentation is done within test code
- https://eclipse-score.github.io/process_description/main/general_concepts/score_building_blocks_concept.html suggests that at least the Integration Tests are represented as sphinx-needs elements
- Expectation is that this would be also done tool supported (i.e. the generation of these sphinx-needs elements from test code)
- This might be done in the build process just to support the documentation (html) gereration
- But maybe we even skip the test spec documentation and create this as part of the test report document (directly from test logs produced by ITF and gtest tools).