[shared_pref]: Bump mockito-inline from 4.7.0 to 5.1.0 in /packages/shared_preferences/shared_preferences_android/android

[dependabot]

Bumps mockito-inline from 4.7.0 to 5.1.0.

Release notes

Sourced from mockito-inline's releases.

v5.1.0

Changelog generated by Shipkit Changelog Gradle Plugin

5.1.0

• 2023-01-29 - 12 commit(s) by Andriy Redko, Ashley, Róbert Papp, Stephan Schroevers, Tim te Beek, dependabot[bot]
• Fixes some mistakes and missing details in documentation [(#2889)](mockito/mockito#2889)
• Bump com.diffplug.spotless from 6.13.0 to 6.14.0 [(#2888)](mockito/mockito#2888)
• Clean up JDK-8 related code [(#2883)](mockito/mockito#2883)
• Feat: reified mock overloads [(#2882)](mockito/mockito#2882)
• Clean up JDK-8 related code [(#2879)](mockito/mockito#2879)
• Bump assertj-core from 3.24.1 to 3.24.2 [(#2875)](mockito/mockito#2875)
• Make sure the tests use mock maker with intended member accessor [(#2872)](mockito/mockito#2872)
• Bump com.diffplug.spotless from 6.12.1 to 6.13.0 [(#2871)](mockito/mockito#2871)
• Remove broken link from CONTRIBUTING.md [(#2870)](mockito/mockito#2870)
• Update outdated badge 3.x to 5.x [(#2869)](mockito/mockito#2869)
• Broken link in CONTRIBUTING.md [(#2868)](mockito/mockito#2868)
• Set current version to 5.x in README and highlight changes [(#2867)](mockito/mockito#2867)
• Annotate Mockito#{mock,spy}(T... reified) with @SafeVarargs [(#2866)](mockito/mockito#2866)
• Make sure the tests use mock maker with intended member accessor [(#2855)](mockito/mockito#2855)
• Improve examples for InOrder [(#2843)](mockito/mockito#2843)

v5.0.0

Mockito 5: prepare for future JDK versions

For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API. Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker. Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working.

Switch the default mockmaker to mockito-inline

Back in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle. This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery. As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior. While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes. For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass.

Massive thanks to community member @​reta who implemented this change.

Note: this does not affect mockito-android nor testing on Android.

When should I still be using the subclass mockmaker?

There are legitimate remaining use cases for the subclass mockmaker. For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice. Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility. Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+. We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker.

If you want to use the subclass mockmaker instead, you can use the new mockito-subclass artifact (published on Maven Central along with all our other artifacts).

... (truncated)

Commits

• 19ab3ea Fixes some mistakes and missing details in documentation (#2889)
• b47bab2 Bump com.diffplug.spotless from 6.13.0 to 6.14.0 (#2888)
• 4775c67 Clean up JDK-8 related code (#2883)
• 91223f8 Feat: reified mock overloads (#2882)
• 96452fa Make sure the tests use mock maker with intended member accessor (#2872)
• 1418769 Bump assertj-core from 3.24.1 to 3.24.2 (#2875)
• f4d7c34 Bump com.diffplug.spotless from 6.12.1 to 6.13.0 (#2871)
• 23e344e Remove broken link from CONTRIBUTING.md (#2870)
• f2a47c3 Improve examples for InOrder (#2843)
• 484de45 Update release badge to 5.x (#2869)
• 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 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)

[dependabot]

Superseded by #334.