Configuration service: Updates to helm charts do not completely replace the previous chart

[bacherfl]

Let's say we have a service foo with the following helm chart:

foo
  -> chart
    -> templates
      -> svc.yml
      -> deployment.yaml

Then we update the chart of the service with a newer version, which has a different structure

foo
  -> chart
    -> templates
      -> service.yml
      -> deployment.yaml

In that case, the configuration service will currently not completely replace the previous chart with the new one, but actually merge those two. The resulting structure will look as follows:

foo
  -> chart
    -> templates
      -> service.yml
      -> svc.yaml // leftover of the previous version
      -> deployment.yaml // this will be correctly replaced

Note: Currently the workaround for this kind of scenario is to recreate the service - the event history will still be kept since the event collections are only deleted once the project containing the service is deleted. Configurations such as slo.yaml files will have to be re-uploaded as well