GitLab

DFMs that include both Java and native code will probably use JNI. This
change introduces a reusable mechanism to load the native library and
register its JNI methods.

Key points:

- There are 3 build variants supported:
  1. Production builds with lld-generated partitions.
  2. Component build (with feature code in a component).
  3. Fallback release build (feature code in the main library)

- For consistency, explicit JNI registration is done in both
  ChromeModern and Monochrome.

- The Test Dummy module is moved over to use this new system. VR will
  join the fun in a follow-on change.

- Currently, modules must supply an explicit JNI registration method.
  Common code will locate this method and call it, at the appropriate
  time, on behalf of the module.

Bug: 870055
Change-Id: Id400ff00b4be65f71536a4acffdfcf93cc3bea58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1822846
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700276}