Fix review app path

Why is this change being made?

Following some changes to review apps recently (!5388 (merged)), the environment path selected means that GitLab no longer sees these as review app environments internally. It seems they need to use review/ as the path so that things like https://docs.gitlab.com/ee/api/environments.html#delete-multiple-stopped-review-apps can work to manage these environments.

Also, !5327 (merged) set all deployments as production for deployment tier, which was fine at that time. But since the change above, review apps are re-using the pages job, and now they are all being labeled as deployments to production. We can remove this hard coding, because GitLab automatically sets the tier to production when the environment name is production. Otherwise, our DORA metrics are probably being skewed by review app deployments: https://docs.gitlab.com/ee/user/analytics/dora_metrics.html#deployment-frequency

• Related to Move development/contributing docs to docsy the... (!5327 - merged)
• Related to Improve review apps (!5388 - merged)
• Related to Update review app environment with a slash '/' (!7082 - merged)

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (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 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
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Fix review app path

---

.vale/handbook/headerlinks.yml

+#
+# Do not include a link in a heading.
+# Headings already have self-referencing anchor links,
+# and they're used for generating the table of contents.
+# Adding a link will break the anchor linking behaviour.
+#
+# For a list of all options, see https://vale.sh/docs/topics/styles/
+extends: existence
+message: "Do not have links in headings."
+level: error
+ignorecase: true
+nonword: true
+link: https://handbook.gitlab.com/docs/markdown-guide/#headings
+scope: raw
+tokens:
+  - ^#+ [^\n]*\[[^\]\n]*\]\([^\)\n]+\)