chore(deps): update net.ltgt.gradle:gradle-errorprone-plugin to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
net.ltgt.gradle:gradle-errorprone-plugin	3.1.0 → 5.0.0

---

Release Notes

tbroyer/gradle-errorprone-plugin (net.ltgt.gradle:gradle-errorprone-plugin)

v5.0.0

• Minimum Gradle version has been bumped to 7.1
• Minimum JDK version has been bumped to 11 (even though this is not guaranteed by tests, Gradle can run with a Java 8 JVM, but must use a JDK 11 toolchain –or newer– for Java compilation)
• isEnabled and isCompilingTestOnlyCode properties have been renamed to enabled and compilingTestOnlyCode in Kotlin DSL, to align with the core Gradle practice of not having such is prefixes in Kotlin DSL, or different property names between Groovy DSL and Kotlin DSL
• other small changes (mostly internal, including a rewrite from Kotlin to Java), but that do not break binary compatibility for common usage, so plugins compiled against previous versions should continue to work

A note regarding the rewrite to Java, before I get questions about it: as much as I like Kotlin, I'm more familiar with Java tooling (specifically Error Prone and NullAway) and Java compatibility rules, and Android Lint is too heavyweight to my tastes.

v4.4.0

Pass -XDaddTypeAnnotationsToSymbol=true (#​132, 672a7af)

It helps NullAway and has been recommended for some time, and Error Prone 2.46.0 now requires it.
It's only needed/useful/required for JDK 21 but it's harmless to pass it unconditionally to any version of JavaC.

v4.3.0

Add support for -XepAllSuggestionsAsWarnings (a9b6516)

v4.2.0

Handle configurations more lazily

This is in preparation for Gradle 8.14 which will no longer realize all configurations in the base plugin, allowing truly lazily-initialized configurations.

This change should allow the javacConfiguration to only be initialized when JDK 8 is being used, and the various annotationProcessor configurations from source sets to only be initialized when needed, e.g. when a compilation tasks for that source set is run (it's likely that the java plugin doesn't yet take advantage of this new possibility itself though)

v4.1.0

• Pass --should-stop=ifError=FLOW to the compiler; it fixes a few issues in all versions of Error Prone, and the next version will make it mandatory (should have been the case in 2.34 already, but didn't actually apply to the JavaC plugin).
• Add metadata to the published POM (#​100)

v4.0.1

Only assign options.isFork if needed

This is a first step in preparation for some changes coming in Gradle 9.

v4.0.0

The errorprone configuration can no longer be resolved. It only exists to declare dependencies, i.e. as a dependency scope configuration.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.