Investigate release workflows

[johanwelgemoed]

Description

There seem to be an issue with the release workflows in that it sometimes uploads the artefact to the wrong tag.
An example of this is on 8.4 release (only one seen so far).
tag 8.4.7 contained the 8.4.8 artefacts
tag 8.4.6 contained both 8.4.6 and 8.4.7 artefacts

I suspect this has to do with the fact that we had to do manual workarounds in the process in order to get it released. Since we decoupled versions, operate is effectively one version ahead of other components. This breaks our release process (still to be fixed).

TODO

Investigate why/how this happened and make needed changes so that artifacfs get uploaded to correct tags.

Additional Information

---

Acceptance Criteria

• Checked if the specific data needs to be provided for the QA process

Definition of Ready - Checklist

• The issue has a meaningful title, description and testable acceptance criteria
• If documentation needs to be updated, an issue is created in the camunda-docs repo, and the issue is added to our Operate project board.
• If HELM charts need to be updated, an issue is created in the camunda-platform-heml repo, and the issue is added to our Operate project board.
• Potential Security risks have been considered
• Cross-team dependencies have been considered