Bump com.google.errorprone:error_prone_annotations from 2.35.1 to 2.36.0

[dependabot]

Bumps com.google.errorprone:error_prone_annotations from 2.35.1 to 2.36.0.

Release notes

Sourced from com.google.errorprone:error_prone_annotations's releases.

Error Prone 2.36.0

Changes:

• Add new matcher interfaces to ErrorProneScanner for AST nodes introduced after Java 11 (e5fd194fa21ef9a01e8d4c72489906247aad81c8)
• Fix compatibility with latest JDK 24 EA builds (google/error-prone@d67bc15)
• Check that --should-stop=ifError=FLOW is set when using the -Xplugin integration (e71db1f369a9367f6f2db34c4fbd006b6d6238fd)

New checks:

• DuplicateBranches: Discourage conditional expressions and if statements where both branches are the same
• RedundantControlFlow: Reports redundant continue statements.

Closed issues: #4633, #4646

Commits

• ab522c7 Release Error Prone 2.36.0
• fc5aade Remove swathes of assume()s on the current runtime version.
• b222ea8 Handle qualified enum elements in MissingCasesInEnumSwitch.
• 332cbfa Support record destructuring in ArgumentSelectionDefectChecker.
• 0db3360 UsafeLocaleUsage: update the proposed fix to use replace(char, char)
• c816c8b StatementSwitchToExpressionSwitch - remove // fall out comments in switches
• b5fa441 Consolidate javadoc plugin version
• 2afd0cf Run StatementSwitchToExpressionSwitch_refactoring over EP.
• 37895d3 Fix snapshot doc publishing after https://github.com/google/error-prone/commi...
• c438756 StatementSwitchToExpressionSwitch: for "assignment switch" and "direct conver...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/security/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/security/backport-2.x
# Create a new branch
git switch --create backport/backport-4929-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6deeaba7d1bdda702bc6d52a6d92fa8f015311ee
# Push it to GitHub
git push --set-upstream origin backport/backport-4929-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/security/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-4929-to-2.x.