build: update patching rules for mockito

[PavelSBorisov]

Description:

Mockito 5.16.0 adds support for java module info and PRs
for the version update are failing tests so I am opening this PR to add preserveExisting() (opted for this approach in order to allow backwards compatibility since I am not a 100% sure that all repos that use mockito are updated to the new version)
Related issue(s):

Fixes #

Notes for reviewer:

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[github-actions]

JUnit Test Report

69 tests  ±0   69 ✅ ±0   7m 20s ⏱️ - 9m 25s
14 suites ±0    0 💤 ±0 
14 files   ±0    0 ❌ ±0 

Results for commit cc1c259. ± Comparison against base commit 4f6bc48.

♻️ This comment has been updated with latest results.

[jjohannes]

@PavelSBorisov my take on this is to remove the rule. We have done this similarly for other cases in the past. Reasoning:

• we want to get the patch list smaller asap
• all projects using this list are on recent versions of all libraries now
• Mockito is "only" a testing dependency. Updating it should not be critical
• In any case, a change is never rolled out automatically. Projects explicitly need to update the plugins. They can update the plugin and Mockito version together.

[PavelSBorisov]

@PavelSBorisov my take on this is to remove the rule. We have done this similarly for other cases in the past. Reasoning:

• we want to get the patch list smaller asap
• all projects using this list are on recent versions of all libraries now
• Mockito is "only" a testing dependency. Updating it should not be critical
• In any case, a change is never rolled out automatically. Projects explicitly need to update the plugins. They can update the plugin and Mockito version together.

@jjohannes alright then, I've removed the rules altogether.

[jjohannes]

The "still a bit shaky" test for the JPMS rules is now failing. But that's a problem in the test setup. I will have a look at that.