Communicate releases for Artefacts, and contributing components

• Tag based releases are documented, highlighting the pertinent changes
• Release history is available
• Releases link to the features/stories involved, and the commits that made the supporting changes
• Jira REL project entry automatically generated linking back to artifacts and tickets
• Stakeholders can subscribe to notifications regarding releases

Acceptance criteria is met. The following are created:

• changelog generation based on commits, Jira tickets (features, stories and REL project link) supporting the repo's own CHANGELOG file
• pipeline jobs are developed to trigger the above and using the changelog create a release in GitLab
• GitLab release is appended to the Jira ticket's Release Notes
• GitLab release is sociliased in a slack channel
• developer portal is updated to reflect the workflow

Examples:

• slack channel: https://skao.slack.com/archives/C02MDNMPWKF;
• Test Tab Release: https://gitlab.com/ska-telescope/ska-tango-images/-/tags/0.3.7
• Jira Ticket: REL-11
• Developer Portal page: https://developer.skao.int/en/latest/tools/software-package-release-procedure.html#release-management 

Future Discussion:

• The current process is fully automated but as a result, it doesn't support manual input into the Changelog. They can be edited after the pipeline is run and the GitLab release is created.