Release workflow

The flow to release a new version and automatic deployment into the krm3int environment is the following:

Open a PR from a branch which contains your feature/bugfix etc. specifing the develop target branch
Make sure it contains a commit (using cz commit) that will trigger the new version bump (see here for details)
Once the PR has been reviewed and accepted your code is merged into develop
To perform the release and deploy open a PR from develop to master, upon merge the release pipeline will perform the cz bump command in the master branch, bumping the new version (that in turn is a commit created automatically with a tag containing the new version), push the bump commit (and it's associated tag) in master branch and rebase the develop branch from the master in order to keep the two branches aligned.
Once the new version is bumped the pipeline will publish the docker image in the images registry ⧉ (a.k.a. GitHub package) and after that release the image in the Kubernetes cluster using the Rancher API

    %%{init: {
    'theme': 'base',
    'themeVariables': {
        'gitBranchLabel0': '#ff0000ff',
        'gitBranchLabel1': '#ff0000ff',
        'gitBranchLabel2': '#ff0000ff'
    }
    }}%%
    gitGraph
        commit id: "Initial"
        branch develop
        checkout develop
        commit id: "Dev setup"

        branch feature
        checkout feature
        commit id: "Feature work"
        commit id: "Bug fixes"
        commit id: "cz commit (version trigger)" type: HIGHLIGHT

        checkout develop
        merge feature id: "PR merged to develop"
        commit id: "Develop updated"

        checkout main
        merge develop id: "PR: develop → master"
        commit id: "cz bump (auto)" type: HIGHLIGHT
        commit id: "v1.2.3 (tag)" type: HIGHLIGHT

        checkout develop
        merge main id: "Rebase develop from master"

        checkout main
        commit id: "Docker image published" type: NORMAL
        commit id: "Deploy to krm3int via Rancher" type: REVERSE