Upgrade fmt-maven-plugin 2.22.1 -> 2.24

[Picnic-Bot]

This PR contains the following updates:

Package	Type	Update	Change
fmt-maven-plugin	build	minor	2.22.1 -> 2.23

---

Release Notes

spotify/fmt-maven-plugin (fmt-maven-plugin)

v2.23

Compare Source

---

• If you want to rebase/retry this PR, check this box

[Picnic-Bot]

Suggested commit message:

Upgrade fmt-maven-plugin 2.22.1 -> 2.24 (#1069)

See:
- https://github.com/spotify/fmt-maven-plugin/releases/tag/2.23
- https://github.com/spotify/fmt-maven-plugin/releases/tag/2.24
- https://github.com/spotify/fmt-maven-plugin/compare/2.22.1...2.24

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[Stephan202]

Release notes not yet available, but updated the suggested commit message anyway.

I also pushed a formatting change suggested by GJF, but it looks off; we may want to flag this upstream.

[github-actions]

Looks good. All 1 mutations in this change were killed.

class	surviving	killed
🎉tech.picnic.errorprone.refaster.test.RefasterRuleCollection$UnexpectedMatchReporter	0	1

Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[Stephan202]

I also pushed a formatting change suggested by GJF, but it looks off; we may want to flag this upstream.

I filed google/google-java-format#1081.

[Picnic-Bot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[Stephan202]

I also pushed a formatting change suggested by GJF, but it looks off; we may want to flag this upstream.

I filed google/google-java-format#1081.

A fix for this issue was released; I filed spotify/fmt-maven-plugin#190 to update the plugin.

[github-actions]

Looks good. All 1 mutations in this change were killed.

class	surviving	killed
🎉tech.picnic.errorprone.refaster.test.RefasterRuleCollection$UnexpectedMatchReporter	0	1

Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[Stephan202]

Rebased branch, upgraded plugin and updated the suggested commit message. @rickie this PR is now ready to go.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[Stephan202]

The build now fails because Jitpack again lost some artifacts. I'll try to prioritize #1314, as that would be the cleanest way to move forward.

[rickie]

Makes sense, rebased!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.