Order issues in unlabelled triage report by assigned username

Sort the unlabelled triage report by username

Dry run:

>>>
* Title: 2020-06-05 Newly created unlabelled issues requiring initial triage
.* Description: Hi Triage Team,

Here is a list of the latest issues without labels in the project.

In accordance with the [Partial triage guidelines](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#partial-triage), we would like to ask you to:

1. Check for duplicates in this project and others (it is common for issues reported in EE to already exist in CE).
1. Add a [type label](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#type-labels).
  - If identified as a bug, add a [severity label](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#severity-labels).
  - If the severity is ~S1 or ~S2, [mention relevant PM/EMs from the relevant stage group from product devstages categories](https://about.gitlab.com/handbook/product/categories/#devops-stages).
1. Add a [group label](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#group-labels).
1. Add a [stage label](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#stage-labels).
1. Add relevant [category](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#category-labels) and [facet](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#facet-labels) labels to facilitate automatic addition of stage and group labels.
1. If needed, [mention relevant domain experts](https://about.gitlab.com/company/team/structure/#expert) if the issue requires further attention.
1. If the issue looks like spam, please [report it](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#reporting-spam-issues)

For the issues triaged please check off the box in front of the given issue.

Once you've triaged all the issues assigned to you, you can unassign yourself with the `/unassign me` quick action.

**When all the checkboxes are done, close the issue, and celebrate!** :tada:

@a_mcdonald

- [ ] gitlab-org/quality/triage-ops#425 Reviewer roulette for WIP MRs looks noisy to (some) contributor and reviewer

@at.ramya

- [ ] gitlab-org/quality/triage-ops#400 Proposal - Move SLO logic for bugs and security issues to severity labels

@caalberts

- [ ] gitlab-org/quality/triage-ops#307 Do not add missed labels on community contributions

@jennielouie

- [ ] gitlab-org/quality/triage-ops#352 Closing MRs when someone is removed from the `gitlab-org`?

@markglenfletcher

- [ ] gitlab-org/quality/triage-ops#483 Plan to remove ~backstage label

@niskhakova

- [ ] gitlab-org/quality/triage-ops#358 Be less verbose when applying labels

@svistas

- [ ] gitlab-org/quality/triage-ops#339 Make the triage process more visible on the issues being triaged

@treagitlab

- [ ] gitlab-org/quality/triage-ops#391 Prompt users of the "Resolve this discussion in a new issue" MR feature to add descriptive titles

@vincywilson

- [ ] gitlab-org/quality/triage-ops#466 Stale Merge Request Triage Report Feedback Issue

/assign @a_mcdonald @at.ramya @caalberts @jennielouie @markglenfletcher @niskhakova @svistas @treagitlab @vincywilson
/label ~Quality ~"triage report"
>>>

Closes #458 (closed)