Enable automated releases (CD) for Job DSL plugin

[MarkEWaite]

Enable automated releases (CD) for Job DSL plugin

Link to GitHub repository

• https://github.com/jenkinsci/job-dsl-plugin

The new release will help with the removal of Apache Commons Lang 2 from Jenkins core. That is currently being tested in:

• [JENKINS-72981] Remove Commons Lang 2 from core jenkinsci/jenkins#16404
• Testing commons-lang2 removal from jenkins-core jenkinsci/bom#6234

Also updates permissions that were missed in previous changes. Completes the removal of @jamietanna and @daspilker as Job DSL maintainers, since they removed themselves with earlier pull requests.

@jamietanna removed himself as a Job DSL maintainer in pull request:

• Remove myself as a Job DSL developer #4404

@daspilker removed himself as a Job DSL maintainer in pull request:

• remove access for daspilker #4385

When modifying release permission

List the GitHub usernames of the users who should have commit permissions below:

• N/A

This is needed in order to cut releases of the plugin or component.

If you are modifying the release permission of your plugin or component, fill out the following checklist:

Release permission checklist (for submitters)

• The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to accounts.jenkins.io.
• All users added have logged in to Artifactory and Jira once.
• I have mentioned an existing team member of the plugin or component team to approve this request.

When enabling automated releases (cd: true)

Follow the documentation to ensure, your pull request is set up properly. Don't merge it yet.
In case of changes requested by the hosting team, an open PR facilitates future reviews, without derailing work across multiple PRs.

Link to the PR enabling CD in your plugin

• Enable automated releases (CD) jenkinsci/job-dsl-plugin#2563

CD checklist (for submitters)

• I have provided a link to the pull request in my plugin, which enables CD according to the documentation.

Reviewer checklist

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