Allow Mark Waite to maintain priority sorter plugin

[MarkEWaite]

Allow Mark Waite to adopt the priority sorter plugin

@MarkEWaite wants to adopt the priority sorter plugin because it will help him while testing new Jenkins releases.

https://github.com/jenkinsci/priority-sorter-plugin is the plugin repository

Some pull requests that I've submitted:

• [JENKINS-66938] Allow 2 or more priority definitions to be saved jenkinsci/priority-sorter-plugin#88 - Fix 4.0.0 bug that configuration can't be saved

Some pull requests that I've reviewed and would like to merge and release:

• Bump plugin from 4.15 to 4.31 jenkinsci/priority-sorter-plugin#86 - Use most recent parent pom
• Spelling fixes and formatting improvements jenkinsci/priority-sorter-plugin#85 - Spelling fixes and formatting improvements
• Bump bom-2.235.x from 25 to 918.vae501d2cdc99 jenkinsci/priority-sorter-plugin#79 - Update bom for plugin dependencies
• Fix for view based priority sorting jelly jenkinsci/priority-sorter-plugin#66 - Fix config won't save bug

Some pull requests that will help me and I'll review after releasing the bug fix:

• [JENKINS-54571] Add Configuration as Code plugin support jenkinsci/priority-sorter-plugin#62 - Configuration as code support

Since the plugin is up for adoption, I hope we can proceed immediately to grant me permission.

Existing maintainers (in case needed for approval):

• @oleg-nenashev
• @emsa23
• @fr123k

Submitter checklist for adding or changing permissions

Always

• Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

• Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
• Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
• Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
• All newly added users have logged in to Artifactory at least once

Reviewer checklist (not for requesters!)

• Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
• Check that the $pluginId Developers team has Admin permissions while granting the access.
• In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
• If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

[oleg-nenashev]

Thanks Mark! Any contributions will be appreciated