Bump com.google.guava:guava from 32.0.1-jre to 32.1.1-jre in /distribution/tools/plugin-cli

[dependabot]

Bumps com.google.guava:guava from 32.0.1-jre to 32.1.1-jre.

Release notes

Sourced from com.google.guava:guava's releases.

32.1.1

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>32.1.1-jre</version>
  <!-- or, for Android: -->
  <version>32.1.1-android</version>
</dependency>

Jar files

• 32.1.1-jre.jar
• 32.1.1-android.jar

Guava requires one runtime dependency, which you can download here:

• failureaccess-1.0.1.jar

Javadoc

• 32.1.1-jre
• 32.1.1-android

JDiff

• 32.1.1-jre vs. 32.1.0-jre
• 32.1.1-android vs. 32.1.0-android
• 32.1.1-android vs. 32.1.1-jre

Changelog

• Fixed our broken Gradle metadata from 32.1.0. Sorry again for the trouble. If you use Gradle, please still read the release notes from that version: You may still see errors from the new checking that the metadata enables, and the release notes discuss how to fix those errors.

32.1.0

Warning: Gradle metadata is broken. Read these notes, but skip to 32.1.1

We made a mistake in our release script, so the new Gradle metadata (discussed below) is broken in 32.1.0. Sorry for the trouble and for the need for another quick patch release. We recommend upgrading straight to release 32.1.1, especially if you use Gradle or if you publish a library whose users might use Gradle. Still, read the release notes below if you use Gradle, since the fixed Gradle metadata in 32.1.1 may still require action on your part.

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>32.1.0-jre</version>
  <!-- or, for Android: -->
</tr></table> 

... (truncated)

Commits

• See full diff 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 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)

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/18943/
• CommitID: be8955e
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/19111/
• CommitID: f15c40f
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/19113/
• CommitID: a4c879b
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[owaiskazi19]

guava 32.1.1-jre brings up 4.11.0 of mockito-core as a transitive dependency: https://mvnrepository.com/artifact/com.google.guava/guava-parent/32.1.1-jre whereas OpenSearch is having 5.4.0 of mockito.

* What went wrong:
Could not determine the dependencies of task ':distribution:tools:plugin-cli:forbiddenApisTest'.
> Could not resolve all task dependencies for configuration ':distribution:tools:plugin-cli:testRuntimeClasspath'.
   > Conflict(s) found for the following module(s):
       - org.mockito:mockito-core between versions 5.4.0 and 4.11.0
     Run with:
         --scan or
         :distribution:tools:plugin-cli:dependencyInsight --configuration testRuntimeClasspath --dependency org.mockito:mockito-core
     to get more insight on how to solve the conflict.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/19435/
• CommitID: 2588780

[codecov]

Codecov Report

Merging #8400 (48e4266) into main (e0e60ee) will increase coverage by 0.08%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #8400      +/-   ##
============================================
+ Coverage     70.86%   70.94%   +0.08%     
- Complexity    56931    56999      +68     
============================================
  Files          4758     4758              
  Lines        269359   269359              
  Branches      39409    39409              
============================================
+ Hits         190873   191107     +234     
+ Misses        62393    62178     -215     
+ Partials      16093    16074      -19     

see 454 files with indirect coverage changes

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/19438/
• CommitID: 48e4266