Add new Release group JTBD

Why is this change being made?

Adds new Job to Be Done for Release group:

When managing changes to production, I want to take action on deployments across my organization from a single place, so I can have better control of our production changes.

This JTBD is based on research insights from the following opportunity canvases and epics:

• How can we make managing planning and executing releases across repos easy?
• How can we help users deploy with GitLab?
• Environments Job To Be Done Evaluation

Production environments are special ones and sometimes we could have several environments that we use as a production. Currently, the growing GitLab roles leave the ability to edit environments and trigger a manual release to production vulnerable.

We want to be able to support environments at the group-level. This would address the nature by which environments were created in, at the project level for project members. The lack of context and ability to manage access when a environment is shared across multiple projects is disruptive to they way teams may work with each other in production.

Share production environments across projects Epic

On the research that led to this canvas, users specifically mentioned expectations and pain-points that point to a centralized location:

• Users are expecting org-level dashboards for pipelines, environments and commits
• Users are frustrated that there is not a single place to see where things are going wrong for deployments
• Users want to seamlessly level down and up from group to project metrics

While most of these refer to managing in a broad sense, we have no JTBD that point to problems specifically with acting on top of information visualized on our environments UI i.e.: approving and rejecting deployments, re-deploying, stopping environments. This JTBD aims to focus on this aspect of the workflow.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)