Do some JIRA/GitHub version syncing

[coverbeck]

Description
Does some syncing of JIRA fix version and GitHub milestone, which Unito does not do.

The syncing problem is because a fix version in JIRA is a multi-value field, whereas the milestone in GitHub is a single-value field.

See JavaDoc in MilestoneResolver.java for further details.

Review Instructions
Describe if this ticket needs review and if so, how one may go about it in qa and/or staging environments.
For example, a ticket based on Security Hub, Snyk, or Dependabot may not need review since those services
will generate new warnings if the issue has not been resolved properly. On the other hand, an infrastructure
ticket that results in visible changes to the end-user will definitely require review.
Many tickets will likely be between these two extremes, so some judgement may be required.

Issue
SEAB-5953

Security
If there are any concerns that require extra attention from the security team, highlight them here.

Please make sure that you've checked the following before submitting your pull request. Thanks!

• Check that you pass the basic style checks and unit tests by running mvn clean install in the project that you have modified (until https://ucsc-cgl.atlassian.net/browse/SEAB-5300 adds multi-module support properly)
• Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
• If you are changing dependencies, check with dependabot to ensure you are not introducing new high/critical vulnerabilities
• If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 45.70%. Comparing base (3703712) to head (1b11435).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff             @@
##             develop     #495   +/-   ##
==========================================
  Coverage      45.70%   45.70%           
  Complexity       319      319           
==========================================
  Files             50       50           
  Lines           2700     2700           
  Branches         210      210           
==========================================
  Hits            1234     1234           
  Misses          1375     1375           
  Partials          91       91           

Flag	Coverage Δ
metricsaggregator	36.70% <ø> (ø)
toolbackup	22.85% <ø> (ø)
tooltester	17.07% <ø> (ø)
topicgenerator	20.29% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarcloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[denis-yuen]

Review instructions not updated

[denis-yuen]

Still missing review instructions, something may have gone awry with the way develop was merged into this branch.

[denis-yuen]

otherwise looks fine, but should clean-up before merge

[svonworl]

Was here, but the diffs look busted, there's lots of changes in there that probably don't relate to yours. Will take another look when it's fixed.

[coverbeck]

I had rebased off an older pull of develop. I updated develop locally and rebased again. Diff should be good now.

[denis-yuen]

Still missing review instructions

[sonarcloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint