Speculatively increase VR controller workaround delay

There's been some more flakiness with VR instrumentation tests that use
the VrCore-side emulated controller. Increasing the amount of time
that's waited before sending the first input event seems to fix this
from some limited testing, so speculatively commit to see if it fixes
the issue on the bots.

Change-Id: If438358d14f410911831911a3b0880902b57ddda
Reviewed-on: https://chromium-review.googlesource.com/1217027Reviewed-by: Aldo Culquicondor <acondor@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589998}

chrome/android/javatests/src/org/chromium/chrome/browser/vr/EmulatedVrController.java

@@ -24,7 +24,7 @@ import java.util.concurrent.TimeUnit;
  */
 public class EmulatedVrController {
     public enum ScrollDirection { UP, DOWN, LEFT, RIGHT }
-    private static final int FIRST_INPUT_DELAY_MS = 500;
+    private static final int FIRST_INPUT_DELAY_MS = 1000;
     private final ControllerTestApi mApi;
     private boolean mHaveSentInputSinceEnteringVr;