[aw] Clean up unneeded evaluateJavaScript in renderer termination tests

Originally the evaluateJavaScript call was present to ensure renderer
startup, but the convenience method now explicitly loads about:blank
synchronously to achieve the same result.

Bug: 865062
Change-Id: I81c19fe7cfe3257f44e379de5f05a5337c92ea4b
Reviewed-on: https://chromium-review.googlesource.com/1154918Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Tobias Sargeant <tobiasjs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579048}

android_webview/javatests/src/org/chromium/android_webview/test/AwContentsClientOnRenderProcessGoneTest.java

@@ -130,11 +130,8 @@ public class AwContentsClientOnRenderProcessGoneTest {
     @CommandLineFlags.Add(AwSwitches.WEBVIEW_SANDBOXED_RENDERER)
     @SkipCommandLineParameterization
     public void testRenderProcessTermination() throws Throwable {
-        createAndTerminateRenderProcess((AwContents awContents) -> {
-            awContents.evaluateJavaScript("0", (String result) -> {
-                Assert.assertTrue(awContents.getRenderProcess().terminate());
-            });
-        }, false);
+        createAndTerminateRenderProcess(
+                (AwContents awContents) -> { awContents.getRenderProcess().terminate(); }, false);
     }
 
     @Test