Rename android_webview_apk and android_webview_test_apk

docs/android_test_instructions.md

 # Android Test Instructions
 
 [TOC]
 
 ## Device Setup
 
 ### Physical Device Setup
 
 #### ADB Debugging
 
@@ skipping 103 matching lines @@
 second directory rather than the top-level one.
 
 ### Java
 
 Java test files vary a bit more widely than their C++ counterparts:
 
 -   Instrumentation test files -- i.e., tests that will run on a device --
     typically belong in either `<top-level directory>_javatests` or `<top-level
     directory>_test_java`. Regardless, they'll wind up getting packaged into one
     of a few test APKs:
-    -   `android_webview_test_apk` for anything in `//android_webview`
+    -   `webview_instrumentation_test_apk` for anything in `//android_webview`
     -   `content_shell_test_apk` for anything in `//content` or below
     -   `chrome_public_test_apk` for most things in `//chrome`
     -   `chrome_sync_shell_test_apk` in a few exceptional cases
 -   JUnit or Robolectric test files -- i.e., tests that will run on the host --
     typically belong in `<top-level directory>_junit_tests` (e.g.
     `base_junit_tests` for `//base`), though here again there are cases
     (particularly in `//components`) where suites are split at the second
     directory rather than the top-level one.
 
 Once you know what to build, just do it like you normally would build anything
@@ skipping 128 matching lines @@
 # Build the tests themselves
 ninja -C out/Release chrome_public_test_apk
 
 # Run the test (will automagically install the APK under test and the test APK)
 out/Release/bin/run_chrome_public_test_apk [-vv]
 ```
 
 AndroidWebView tests:
 
 ```shell
-ninja -C out/Release android_webview_apk
-ninja -C out/Release android_webview_test_apk
-out/Release/bin/run_android_webview_test_apk [-vv]
+ninja -C out/Release webview_instrumentation_apk
+ninja -C out/Release webview_instrumentation_test_apk
+out/Release/bin/run_webview_instrumentation_test_apk [-vv]
 ```
 
 In order to run a subset of tests, use -f to filter based on test class/method
 or -A/-E to filter using annotations.
 
 Filtering examples:
 
 ```shell
 # Run a test suite
 out/Debug/bin/run_content_shell_test_apk
@@ skipping 20 matching lines @@
 
 See [Layout Tests](testing/layout_tests.md).
 
 ## Running GPU tests
 
 (e.g. the "Android Debug (Nexus 7)" bot on the chromium.gpu waterfall)
 
 See https://www.chromium.org/developers/testing/gpu-testing for details. Use
 `--browser=android-content-shell`. Examine the stdio from the test invocation on
 the bots to see arguments to pass to `src/content/test/gpu/run_gpu_test.py`.