First iteration of priorities for People Group Engineering

Why is this change being made?

As the team and the need for People Tools is maturing, we need a better system to triage based on the priority of issues. This is a first iteration of doing so. Once this is approved, I will have a look at our current issues and label them. I deliberately kept it within 5 levels of priority, as I think more will make it overly complicated (and that's also following the way GitLab engineering does it for the product).

Note, this goes hand-in-hand with an update on the new issue template, which you can find here. The changes on that template include:

• a checkbox for compliance
• guided questions to know the impact on the company and on time

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)