[Idea 💡] Update release candidate deployment process

[rpothin]

A few points we are thinking of covering in this issue:

• Remove the creation of release branches and only base the identification of version deployed to production using tags (created with GitHub releases)
• Integrate the creation of a GitHub release and deployment to the Production environment directly after the deployment to the Validation environment
  • Major version considered for the solution managed in a configuration file
  • Find a better way to automatically generate GitHub release body regarding what has been changed (idea Automatically generated release notes)
• Confirm that the same commit is used in the different jobs of a GitHub workflow for the deployment of a release candidate (should be ok based on the information in the page of the checkout action)