Backend deployment process

[szabozoltan69]

• Update CHANGELOG.md (for major releases also git tag).
• Merge the go-api feature branch to develop branch
• (or the required branch (probably develop) to master branch)
• After finishing the Builds and pushes Docker Images and Helm charts to GitHub Registry step on GitHub,
  on https://github.com/ifrcgo/go-api/pkgs/container/go-api%2Fifrcgo-helm there is a new image appearing at top,
  e.g. 0.0.1-0.dev.git.1.hf3937bd
  (Which is: "0.0.1-0.dev.git.1.h" + the first seven characters of the last git commit.)
  Check the creation time and the commit id, then if good: copy that image name to your clipboard.
• https://github.com/IFRCGo/go-deploy/blob/develop/applications/go-api/azure-pipelines.yaml - edit this.
  Put the copied image name to the "develop" code, to here, in case of "develop" (Staging deployment):

      ENVIRONMENT: staging
      VERSION: "0.0.1-0.dev.git.1.hf3937bd"

or downer here, in case of "master" (Production deployment):

      ENVIRONMENT: production
      VERSION: "0.0.1-0.dev.git.1.hd558a46"

The commit message of this change can be relevant, e.g. the summary of the topic we deploy.
(This will appear on the Azure DevOps pipeline.)

• In case of go-api Production deployment, merge the go-deploy "develop" branch to "master":
  IFRCGo/go-deploy@master...develop
• This go-deploy change will initiate the deployment. (Two pipelines get green on Azure DevOps.)
• At the end of deployment (which is 2-3 minutes) log in to the remote vm and check git log.
• If there are manage.py commands to run manually after deployment, please check the migrations (if any) to be finished.

[szabozoltan69]

@thenav56 @susilnem @batpad @samshara – this can be useful in the next weeks.