Simplify error-prone refactoring code

[CRogers]

Before this PR

Now we've upgraded to recent errorprone, there are some workarounds we had for bugs that are no longer necessary. Now that google/error-prone#3908 is fixed (and released in 2.26.0) we can avoid explicitly disabling checks when patching.

After this PR

==COMMIT_MSG==
Simplify error-prone refactoring code
==COMMIT_MSG==

Possible downsides?

[changelog-app]

Generate changelog in changelog/@unreleased

What do the change types mean?

• feature: A new feature of the service.
• improvement: An incremental improvement in the functionality or operation of the service.
• fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
• break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
  and external consumers of the service's API (e.g. customer-written software or integrations).
• deprecation: Advertises the intention to remove service functionality without any change to the
  operation of the service itself.
• manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
  performing database surgery, ...) at the time of upgrade for it to succeed.
• migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?

• ❗The break and manual task changelog types will result in a major release!
• 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
• ✨ All others will result in a minor version release.

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Simplify error-prone refactoring code

Check the box to generate changelog(s)

• Generate changelog entry

[CRogers]

I was expecting this change to fail this test, but it is actually working 🤔

[CRogers]

I think the tests in BaselineErrorProneIntegrationTest are very broken, they still pass if you stop disabling the checks.

[carterkozak]

I recall some configuration ordering issues where checks may be configured before the gradle-baseline defaults are applied and override error-prone settings