[Error-prone] Add InlineMeInliner to default patch checks

[aldexis]

Before this PR

When libraries specify @InlineMe annotations like in https://github.com/palantir/deadlines-java/pull/188/files#diff-f8f90c9951b97fc3abe992cb927e3601222e7e3ce25efb471821039feab57432R179-R181, the current behavior would just suppress it (example), when we could instead apply the proposed fix, which is more desirable.

After this PR

==COMMIT_MSG==
[Error-prone] Add InlineMeInliner to default patch checks
==COMMIT_MSG==

Possible downsides?

This means that external libraries could in theory change your code through the use of InlineMe annotations, but given they could also just change their own code, this doesn't change too much.

[changelog-app]

Generate changelog in changelog/@unreleased

Type (Select exactly one)

• Feature (Adding new functionality)
• Improvement (Improving existing functionality)
• Fix (Fixing an issue with existing functionality)
• Break (Creating a new major version by breaking public APIs)
• Deprecation (Removing functionality in a non-breaking way)
• Migration (Automatically moving data/functionality to a new system)

Description

[Error-prone] Add InlineMeInliner to default patch checks

Check the box to generate changelog(s)

• Generate changelog entry

[changelog-app]

✅ Successfully generated changelog entry!

What happened?

Your changelog entries have been stored in the database as part of our migration to ChangelogV3.

Need to regenerate?

Simply interact with the changelog bot comment again to regenerate these entries.

[CRogers]

The only other issue could be external usages of @InlineMe not compiling when inlining, without us easily being a being able to fix. We have the same problem with Google's built in errorprones though, and can always revert this if it causes issues.

[CRogers]

👍

[autorelease3]

Released 6.60.0