Make tagging process automatic

BEGINRELEASENOTES

*tests NEW: Automate tagging process

ENDRELEASENOTES

There are now two new jobs in the pipeline (start_tag and create_tag). To start the tagging procedure, you wait until the pipeline has passed, then you can manually trigger start_tag and create_tag depends on this.

1. If you don't specify any variable when triggering a new tag will be made and only the LHCbDIRAC version will be updated for p=p+1, other dependencies versions will be taken from the previous release.

2. You can specify the variables at triggering of start_tag to specify a desired version:

   • DIRAC
   • LHCbDIRACOS
   • LHCbWebDIRAC
   • If you omit any of these variables the version from the previous release will be used

To specify the variables use the key value from the manual trigger window

The first job will prepare all the files needed to create and release. The second job makes a checkout with the LHCbDIRAC bot account and pushed back the update to CHANGELOG/{series}, releases.cfg, __init__.py, Dockerfile to the branch the release is made and updates the devel branch content of CHANGELOG/{series}, releases.cfg if a tag has been made from master

3. If you want to force a specific release then use the variable NEXT_RELEASE then this version will be used. This is mostly applicable when you do a first release of a new series.

I still need that this is merged since currently I use the version from my fork.

As test drove this as much as possible on my repo, but maybe some final polishing is needed on the main repo.