Fork dexmaker-mockito-inline (https://github.com/linkedin/dexmaker/tree/main/dexmaker-mockito-inline) to replace the subclass-based mock maker with a JVMTI-based inline mock maker that supports mocking final classes and methods on Android.

This allows Mockito to be useful in a modern Kotlin Android ecosystem where classes are final by default unless explicitly marked with the open keyword. The subclass mock maker cannot mock final classes, and the inline mock maker does not work on Android.

Users currently work around this limitation by:

• avoiding mocking unowned Kotlin code and adding open to owned Kotlin classes they want to mock
• or running tests on JVM with a simulated Android environment via Robolectric
• or using MockK (note: they similarly forked dexmaker-mockito-inline in 2018: https://github.com/mockk/mockk/tree/master/modules/mockk-agent-android)

Risks/Considerations:

• Backwards compatibility
  • I think changing mockito-android distribution from jar to aar will be transparent for Gradle users, but not sure about other build systems.
  • Now requires min API 28 (Android P) - the instrumentation test build will fail if the test's manifest specifies a lower min SDK. According to the Android Studio version distribution dialog, Android P+ covers 95% of Android users. We may have Mockito users running tests on pre-API 28 emulators, but we can encourage them to stay on an older version of mockito-android or upgrade the tests to run on a newer API.
• Forking
  • Instead of forking, we could probably simply depend on the dexmaker-mockito-inline artifact. The downside of this seems to be lack of control and limiting future improvements.
• Licensing
  • external/:
    • jdk/jvmti.h is from Oracle OpenJDK under GPL-2.0
    • slicer/ is from AOSP under Apache 2.0
  • agent.cc and all new Java sources except InlineAndroidMockMaker.java are copied from dexmaker-mockito-inline licensed under Apache 2.0. Confusingly, the headers of these sources state "Copyright (C) 2017 The Android Open Source Project" even though they seem to originate from the dexmaker repo itself. I opened License headers? linkedin/dexmaker#208 asking about this. I retained the headers as-is.
• Dispatcher
  • dexmaker-mockito-inline includes a pre-built dispatcher.jar with dex bytecode to allow instrumenting methods with JVMTI. I followed the pattern of MockK and build the dispatcher from source instead of having a prebuilt.

Technical changes:

• Convert mockito-android from Java library (JAR) to Android library (AAR) to allow packaging native code
• Add native NDK/CMake code (JVMTI agent + AOSP slicer library)
• Fork dexmaker Java sources under org.mockito.android.internal.creation.inline
• Add InlineAndroidMockMaker entry-point delegating to InlineDexmakerMockMaker
• Build dispatcher.jar via new mockito-android-dispatcher submodule
• Require min SDK 28 (Android P) via manifest for JVMTI support
• Conditionally include mockito-android in the Gradle project based on Android SDK availability
• Add integration tests for final class mocking

Note for reviewers: the only "new" code is InlineAndroidMockMaker.java. Everything else is a copy/fork.

Fixes #3788

Checklist

• Avoid other runtime dependencies

This adds a new compile dependency for mockito-android on com.linkedin.dexmaker:dexmaker which allows runtime generation of Android dex byte code, similar to Byte-Buddy on the JVM.