Upgrade Error Prone 2.30.0 -> 2.31.0

[Picnic-DevPla-Bot]

This PR contains the following updates:

Package	Type	Update	Change
Error Prone (source)		minor	2.30.0 -> 2.31.0
Error Prone (source)	compile	minor	2.30.0 -> 2.31.0

---

Release Notes

google/error-prone (Error Prone)

v2.31.0: Error Prone 2.31.0

Compare Source

This is the last planned minor release of Error Prone that will support running on JDK 11, see #​3803. Using Error Prone to compile code that is deployed to earlier versions will continue to be fully supported, but will require using JDK 17 or newer for compilation and setting --release or -source/-target/-bootclasspath.

Changes:

• Introduce @ThreadSafeTypeParameter with enforcement by ThreadSafe
• Improved support for latest JDK 24 EA builds
• Error Prone is now distributed as a Multi-Release jar (#​3756)

New checks:

• AutoValueBoxedValues: AutoValue instances should not usually contain boxed types that are not Nullable. We recommend removing the unnecessary boxing.

Full changelog: google/error-prone@v2.30.0...v2.31.0

---

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

[Picnic-DevPla-Bot]

Suggested commit message:

Upgrade Error Prone 2.30.0 -> 2.31.0 (#1314)

See:
- https://github.com/google/error-prone/releases/tag/v2.31.0
- https://github.com/google/error-prone/compare/v2.30.0...v2.31.0

[Stephan202]

This requires a new release of our Error Prone fork. This is a bit more involved than usual, as the Error Prone build now has a toolchains setup that appears incompatible with Jitpack. I'll look into this in the coming days.

[Stephan202]

Updated the fork. Turns out we hit issue jitpack/jitpack.io#5795.

[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-DevPla-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.

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

[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