Provide pipeline names for steps and selectors

[zbynek]

This makes it easier to use the plugin with pipeline.

jiraMarkVersionReleased jiraDescription: 'New Features', jiraProjectKey: 'JENKINS', jiraRelease: '1.0.0'
jiraCreateVersion jiraProjectKey: 'JENKINS', jiraVersion: '1.0.0'
jiraCommentIssues issueSelector: matchKeys('JENKINS-1,JENKINS-2'), labels: []
jiraUpdateIssueField fieldId: '10000', fieldValue: 'val', issueSelector: matchKeys('JENKINS-1,JENKINS-2')
jiraWorkflowUpdateIssues jqlSearch: 'text~"aaa"', workflowActionName: 'myAction'
jiraCreateReleaseNotes(jiraEnvironmentVariable: 'RELEASE_NOTES', jiraFilter: 'status in (Resolved, Closed)', jiraProjectKey: '', jiraRelease: '') {
    // some block
}

Instead of matchKey the steps can also use matchJql, matchChanges and matchChangesP4.

Related issue

#101

Changes

Provide pipeline names for steps and selectors.

Tests

• I have updated/added relevant documentation in the docs/ directory
• I have verified that the Code Coverage is not lower than before / that all the changes are covered as needed
• I have tested my changes with a Jira Cloud / Jira Server

[rantoniuk]

Thanks for resurrecting this old feature request!

• I added some re-wording change suggestions for consistency

• Could you also extend / update [the documentation](https://jenkinsci.github.io/jira-plugin/#/usage-examples that lives in the docs/?

[zbynek]

I applied your suggestions butI'm not sure about the consistency. I'd prefer to have jira<verb><subject> where possible, rather than jira<subject><verb>, i.e. keep jiraCreateVersion and jiraMarkVersionRelesed (ideally the latter should be just jiraReleaseVersion, but that symbol is already used) . If we go with the other word order, we should probably also use jiraWokflowExecute / jiraIssueFieldUpdate / jiraReleaseNotesCreate.

[rantoniuk]

I looked at other plugins and I agree with you, so:

• change the Version ones to conform to the jira<verb><subject> format
• update/extend the docs

and this should be good to go.