Implement release and deployment mechanisms for the SDP

AC1 and AC2 (ORCA): We generated the  EDA configuration for SDP , which is saved in the "data" folder within the chart. This was first released with SDP 0.18.1 ( REL-1180 ).  The  Taranta dashboard file , which was already part of the ska-sdp-integration repository, has been also moved to the data directory within the chart, and is part of SDP 0.18.1. As such, one can obtain the files by downloading the chart's tgz file and extracting it. In addition, they are linked to the REL ticket in the description, under "Ancillary products". This method was agreed to with FO and Capability owners. AC3 (YANDA) It is clear that the current deployment at the ITF does not use the CI scheme. It uses the umbrella chart as presented in  https://gitlab.com/ska-telescope/aiv/ska-low-itf.git Indeed after a number of test deployments in Azure I found that the only way to deploy the SDP into a running deployment was to "redeploy" the umbrella chart. AIV confirmed this in a slack conversation.   From Alex Hill (AIV) So the way we work, updating a subcomponent means updating our Helm chart’s dependencies and values if necessary, and just doing a Helm upgrade - letting Helm take care of tearing down what needs to be replaced etc. In that sense we don’t ever deploy a component into a larger running deployment, we just upgrade the larger deployment.It’s a kind of tricky problem though. One-Helm-chart-to-rule-them-all will be OK when the software is stable. But for now, we frequently need to fix bugs and then deploy the development versions, and it’s a bit of a nightmare to do that when you want to bump e.g. ska-low-cbf-proc, which is a dependency of ska-low-csp, which is a dependency of our ska-low-telescope chart - at leach level of the hierarchy starting at the bottom, you have to build a new chart in the pipeline, then update the dependencies in the level above. I’m not sure what the solution is but it makes me feel like maybe we’re doing microservices wrong. Suggestions welcome…(It’s possible to just override the image that a sub-chart uses through Helm values, but if the newer version contains any changes to the chart itself, then that’s no good…) As far as the latest SDP is concerned.  G.Hodosan  has noted that a latest umbrella chart that works is here:  https://gitlab.com/ska-telescope/ska-jupyter-scripting/-/merge_requests/79 Perhaps subsequent features need to determine a more robust way to deal with the dependencies is required.