CI: Automate hot-fix release procedure

[sergiimk]

Let's imagine we have released:

• kamu-node-0.1.0
• kamu-node-0.2.0

We then notice a major bug on prod where 0.1.0 is deployed.

We cannot fix a bug in 0.2.1 because of the risk deploying all major changes in 0.2.0 to prod without sufficient testing.

We therefore decide to create a fix based off 0.1.0 and release it as 0.1.1.

With current CI setup this is very hard to do:

• I created a branch called v0.1.1 and tried to tag it as v0.1.1 - while git permits it, this causes ambiguity issues in refs between a branch and a tag name (even though they point to the same commit) - we need to pick some naming scheme for hot-fix branches (e.g. release/v0.1.1)
• We should verify that release CI action works correctly on such tags:
  • check that it builds artifacts from correct commit
  • check that it creates a GH release with correct name and pointed to correct tag
• When release action finishes, the release-images action will run based off master - we should make sure release-images checks out the same commit that release action was running for.

Same changes should be done in kamu-cli repo.

Another problem to figure out is how to release a hot-fix version of a helm chart. We may want to create a helm-charts CI action that can be parametrized with exact release and make so that kamu-node release automatically triggered it with correct version.