Migrate Yanda-maintained artefacts to CAR

Software artefacts in the old nexus repository, do not conform to the basic naming standards and version conventions.

The Central Artefact Repository has been integrated with automation services that ensure published artefacts are consistently named, and versioned and also have adequate metadata attached that enable the artefact to be traced back to the originating repository.

By completing the migration of artefacts, it will ensure that artefacts meet the present standards, and are stored in a managed solution fit for production support.

• Determine artefact dependencies that need migrating to CAR, and order of migration
• The gitlab-ci templates have been modified to support publishing multiple artefacts (of the same type) per repository.
• The CI pipelines have been amended to use the gitlab-ci templates.
• All necessary artefacts of type pypi, docker, helm, ansible, conan and raw have been migrated to CAR

CAR migration spreadsheet:
https://docs.google.com/spreadsheets/d/14no7bl6qaNzCwtAi9UwtteDIDtCy-QmQE-yS4VGZ4Sc/edit#gid=144648010

The envisaged projects and artefacts were migrated as planned. That included name changes for compliance with the convention and so the new gitlab pointers for convenience.

• ska-sdp-jacal (was jacal): https://gitlab.com/ska-telescope/ska-sdp-jacal
• ska-cpp-template (was cpp-template): https://gitlab.com/ska-telescope/templates/ska-cpp-template
• ska-sdp-plasmastman (was plasma-storage-manager): https://gitlab.com/ska-telescope/ska-sdp-plasmastman
• icrar-leap-accelerate: https://gitlab.com/ska-telescope/icrar-leap-accelerate
• ska-sdp-continuum-imaging-pipelines: https://gitlab.com/ska-telescope/sdp/ska-sdp-continuum-imaging-pipelines