Upgrade Error Prone 2.23.0 -> 2.24.0

[Picnic-Bot]

This PR contains the following updates:

Package	Type	Update	Change
com.google.errorprone:error_prone_annotations (source)	compile	minor	2.23.0 -> 2.24.0
com.google.errorprone:error_prone_core (source)		minor	2.23.0 -> 2.24.0
com.google.errorprone:error_prone_test_helpers (source)	compile	minor	2.23.0 -> 2.24.0
com.google.errorprone:error_prone_core (source)	compile	minor	2.23.0 -> 2.24.0
com.google.errorprone:error_prone_check_api (source)	compile	minor	2.23.0 -> 2.24.0
com.google.errorprone:error_prone_annotation (source)	compile	minor	2.23.0 -> 2.24.0

---

Release Notes

google/error-prone (com.google.errorprone:error_prone_annotations)

v2.24.0: Error Prone 2.24.0

Compare Source

New checks:

• MultipleNullnessAnnotations: Discourage multiple nullness annotations
• NullableTypeParameter: Discourage nullness annotations on type parameters
• NullableWildcard: Discourage nullness annotations on wildcards
• SuperCallToObjectMethod: Generalization of SuperEqualsIsObjectEquals, now covers hashCode

Full Changelog: google/error-prone@v2.23.0...v2.24.0

---

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

[Picnic-Bot]

The Java Platform team wishes you a happy festive period. Here is the suggested commit message:

Upgrade Error Prone 2.23.0 -> 2.24.0 (#935)

See:
- https://github.com/google/error-prone/releases/tag/v2.24.0
- https://github.com/google/error-prone/compare/v2.23.0...v2.24.0
- https://github.com/PicnicSupermarket/error-prone/compare/v2.23.0-picnic-1...v2.24.0-picnic-1

Renovate be like

Header generated and modified from Sweaterify.

[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]

Updated the suggested commit message and added a commit to fix the build.

[rickie]

A quick search didn't show any changes related to Refaster, (maybe good to check) but it would be nice to ensure that there are no incompatibilities 🤔. If we merge this, we skip a version of Error Prone and jump from 2.22.0 -> 2.24.0. Could be fine but just making sure we deliberately make the choice :).

[Stephan202]

git diff v2.23.0..v2.24.0 --name-only shows no Refaster changes indeed. I think this confirms compatibility:

mvn clean install -Dverification.skip -DskipTests -Dversion.error-prone-orig=2.23.0 && mvn clean install -Pself-check

[rickie]

Would it be nice to add this as a note to Renovate such that it will give this as a note for next release as well? Maybe only for this repository though.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
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.

[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]

Would it be nice to add this as a note to Renovate such that it will give this as a note for next release as well? Maybe only for this repository though.

I've started work on a script to assess the full compatibility matrix. It's heavy WIP, would the idea is that it'd generate the input for a Jekyll page. This does of course require that we finally update the website branch. I'll look into that first, which is why I'll now merge this PR, as it should allow undoing some workarounds for google/error-prone#4157.

[Stephan202]

I've started work on a script to assess the full compatibility matrix.

This turned into #938.