Android: Fix running junit4 tests with incremental install

Was broken in several ways:
1. Permissions were not being granted upon install.
2. Needed custom logic to look at instrumentation name in meta-data.
3. BootstrapApplication logic needed to use the correct component name.
   This logic has always been wrong, but never an issue until now.
4. BaseChromiumAndroidJUnitRunner needs to tell the Junit TestRequestBuilder
   the location of all incremental dex files. This would actually also
   be an issue when using AndroidJUnitRunner directly, except that
   test_runner.py passes an explicit list of classes gleaned via
   proguard, so no "find all classes" logic is needed in this case.

Bug: 762024
Change-Id: Ibc3880fdff14829d74926d1c576114b8551a5c9f
Reviewed-on: https://chromium-review.googlesource.com/688715
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Yoland Yan <yolandyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506296}

CrOS-Libchrome-Original-Commit: ca127560828fdaa1f72d81d7b81c2eabe61b2cd2
1 file changed
tree: c12a666c1ab569a24467b2723e1d89f9bda9ead2
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/