Bump Mockito dependencies

[reta]

Description

Bump Mockito dependencies

Issues Resolved

N/A

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (d71c77f) 81.90% compared to head (c35d685) 81.94%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1711      +/-   ##
============================================
+ Coverage     81.90%   81.94%   +0.04%     
- Complexity     4391     4396       +5     
============================================
  Files           421      421              
  Lines         17438    17438              
  Branches       1853     1853              
============================================
+ Hits          14283    14290       +7     
+ Misses         2417     2411       -6     
+ Partials        738      737       -1     

Flag	Coverage Δ
ml-commons	81.94% <ø> (+0.04%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ylwu-amzn]

@reta , should we backport this to 2.x branch ? If yes, can you help add backport 2.x label and backport to 2.x?

[reta]

@reta , should we backport this to 2.x branch ? If yes, can you help add backport 2.x label and backport to 2.x?

Thanks @ylwu-amzn ! Yes, we need to backport but I cannot add labels (only maintainers could do that), sorry about it

[opensearch-trigger-bot]

The backport to 2.x failed:

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

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-1711-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e3a8a5925092db6018124323924b8157b3bf44e9
# Push it to GitHub
git push --set-upstream origin backport/backport-1711-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

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

[ylwu-amzn]

@reta , should we backport this to 2.x branch ? If yes, can you help add backport 2.x label and backport to 2.x?

Thanks @ylwu-amzn ! Yes, we need to backport but I cannot add labels (only maintainers could do that), sorry about it

Got it, I added the label. But seems there are some conflicts, you need to backport manually @reta