Jira integration: support multiple work item tickets per commit

[davidalpert]

Expected Behavior

Sometimes a single conventional commit can fix or resolve several work item tickets at once. In the case of Jira, for example, this might look like a commit message that includes multiple Jira issue keys:

fix: that annoying bug that's been reported by everyone

resolves: JIRA-1111, JIRA-1112, JIRA-1113
related-to: JIRA-1110

In this case, it would be useful to make all of the work items available to the template.

Actual Behavior

Only the first matching work item / Jira issue key is matched.

Steps to Reproduce (including precondition)

• update ./testdata/gitlog_jira.txt so that a commit has more than one Jira key in it

  @@__CHGLOG__@@HASH:14ef0b6d386c5432af9292eab3c8314fa3001bc7	   14ef0b6d@@__CHGLOG_DELIMITER__@@AUTHOR:tsuyoshi wada	mail@example.com 1515153600@@__CHGLOG_DELIMITER__@@COMMITTER:tsuyoshi wada	mail@example.com 1515153600@@__CHGLOG_DELIMITER__@@SUBJECT:fix: Feature didn't work right@@__CHGLOG_DELIMITER__@@BODY:This is body message.
  
  Fixes JIRA-1112, JIRA-1113, JIRA-1114
  Relates-To JIRA-1110
  

• all the unit tests still pass, the commit parser finds only 2 commits and populates the single .JiraIssueID with the first issue ID found but the additional IDs are not available on the parsed commit object.

Your Environment

• OS: GOOS=darwin GOARCH=arm64
• git-chglog version: v0.15.4-5-g8ec17f6

[davidalpert]

this is a bit larger piece of work as it will either change the structure for referencing Jira tickets in existing templates or increase complexity to maintain backwards compatibility; as such I prefer to receive feedback on existing open pull requests to ensure that I am following appropriate style and this work is aligned with the purpose of this tool:

• feat: recognize Jira issue keys in commit body #257
• feat: expose JiraIssue.BaseURL and JiraIssue.BrowseURL #258
• feat: support passing arbitrary key=value pairs #262