Adding Leading Organizations to the prioritization list

Why is this change being made?

There has been discussion on how to do prioritization for community contributions. We recently added a new initiative called Leading Organizations, where these organizations are entitled to an objective of 4 working days in which they should get a review that brings their MR closer to either a merged or closed state. This is proposal to add MRs from our Leading Organizations to our prioritization list so that it is clear what to do when we are in doubt. An earlier discussion can be seen at https://docs.google.com/document/d/1D5JdVVOMshVWp-9DANaRKFgLlLCrT4LAqQDo6_vJCdo/edit#bookmark=id.m2g0yiighfvm.

Initially it was part of the same list, this is now split out to 2 lists, so that it becomes an orthogonal decision tree.

Pages impacted

Why 3? It's embedded in these pages

1. https://about.gitlab.com/handbook/engineering/development/principles/ vs https://nick-vh-master-patch-73975.about.gitlab-review.app/handbook/engineering/development/principles/
2. https://about.gitlab.com/handbook/engineering/quality/quality-engineering/bug-prioritization vs https://nick-vh-master-patch-73975.about.gitlab-review.app/handbook/engineering/quality/quality-engineering/bug-prioritization
3. https://about.gitlab.com/handbook/product/product-processes vs https://nick-vh-master-patch-73975.about.gitlab-review.app/handbook/product/product-processes

How does it look like?

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.
• 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
• 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.

---