Reintegrate single software components into SKAMPI

In PI13 we will continue re-integrating different software components as part of SKAMPI, following the revised repository structure and CI automations.

Milestones should be identified at PI planning representing the integration events so that an integration timeline can be populated with details for PI13. 

Possible components include: TMC, OET, MCCS, SDP, CSP LMC, Taranta (already happening at the end of PI12), skuid.

For each component it shall be evaluated what level of testing is achievable in the current configuration of the SKAMPI platform. If end-to-end tests that exercise the single component can be executed this should always take precedence. Execution of acceptance tests defined at component level also provides valuable information. 

For each component we will strive to have:

• to be migrated to pipeline machinery, common directory structure, standard poetry and pytest implementation
• component tests that target standalone and integrated scenarios (identified by marks)
• published image that also contains tests, poetry.lock, pyproject.toml, and tests/pytest.ini
• a component helm chart that integrates into an umbrella chart
• an implementation review covering deployment architecture, performance and test coverage
• a code review based around an integration Merge Request
  • both as part of the cross team review process
• fitness for integration acceptance from the owners
• merging and releasing (REL process)