✨ Handling of staging hotfixes

[sanderegg]

What do these changes do?

Adds the option to create a staging-hotfix release by following the same rules as for release-hotfixes:

• create a branch named such as staging_meerkat2
• wait for the CI to complete the normal build -> will generate images named such as webserver:hotfix-staging-github-latest and webserver:hotfix-staging-github-DATE-SHA
• if ok, then using make release-hotfix-staging creates a TAG that the github CI will pickup
• the CI will then rename the previously created images to staging-github-latest so that it gets deployed

Related issue/s

How to test

Checklist

[codecov]

Codecov Report

Merging #2649 (1029639) into master (ff21b4a) will increase coverage by 0.0%.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2649   +/-   ##
======================================
  Coverage    77.1%   77.1%           
======================================
  Files         625     625           
  Lines       25148   25148           
  Branches     2475    2475           
======================================
+ Hits        19392   19398    +6     
+ Misses       5112    5109    -3     
+ Partials      644     641    -3     

Flag	Coverage Δ
integrationtests	65.0% <ø> (+<0.1%)	⬆️
unittests	73.0% <ø> (+<0.1%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
.../director/src/simcore_service_director/producer.py	62.1% <0.0%> (+0.4%)	⬆️
...ce_webserver/resource_manager/garbage_collector.py	76.4% <0.0%> (+0.8%)	⬆️
...car/src/simcore_service_dask_sidecar/dask_utils.py	90.4% <0.0%> (+1.1%)	⬆️
...rc/simcore_service_director_v2/modules/rabbitmq.py	89.4% <0.0%> (+1.7%)	⬆️

[GitHK]

👍 nice addition