Adopt extended-read-perms

[NotMyFault]

Looking forward to modernizing the plugin and delivering jenkinsci/extended-read-permission-plugin#18

cc @batmat @oleg-nenashev

Description

Submitter checklist for adding or changing permissions

Always

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

When enabling automated releases (cd: true)

• Add a link to the pull request, which enables continuous delivery for your plugin or component.
  Follow the documentation to ensure, your pull request is set up properly.

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 and Jira 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 @Wadeck) 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]

+1