🚀 Enhancing Release workflow

[pcrespov]

After several rounds of manual releases, we should start formalizing the workflow so that anybody in the team can reliably release.

• Move latest ticket templates from osparc-issues -> osparc-simcore
• scripts to create release issues
  • given pre/release name and version and SHA -> creates issue with draft release link and steps to follow
• scripts announcements using status.osparc.io API (related to Notify users in the front-end when the status page issues maintenance or incident  #4080 )
• Move ALL release issues from osparc-issues to osparc-simcore repo Won't do. It will break existing hard-coded links

SEE

• https://github.com/ITISFoundation/osparc-simcore/releases
• https://github.com/ITISFoundation/osparc-issues/issues?q=is%3Aissue++label%3Arelease+ (soon to be moved to osparc-simcore)

[pcrespov]

Added label release in osparc-simcore repo as well