Improve discoverability of MR workflow labels

Why is this change being made?

The ~"workflow::" labels are typically used in Issues, as extensively described in the product development flow.

We do use some ~"workflow::" labels in merge requests to indicate the stage of deployment the MR is in. This information is currently hard to discover because the SSOT of labels utilized is not in the handbook, but in an infra project.

This MR improves discoverability by adding content to a FAQ item. This result should be present in searches about the topic.

Author Checklist

• 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
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---