Reduce the time to ignore PointerLock requests after a lock exit.

We encountered use-cases where the user hits the Esc key to release a
PointerLock then expects to request another lock soon afterwards.  If
the second request comes within 2secs of the Esc keypress, we have been
deliberately ignoring the second request to suppress abusive uses of
requestPointerLock (e.g. to prevent users from exiting the locked state,
see crbug.com/1084618).

To address the above problem while also preventing abusive uses, this CL
reduces the delay to 1.25sec as a trade-off.

Fixed: 1127223
Change-Id: I37a5e8e16e8387ac4717fc90fecf946257199575
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505911Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#822137}

chrome/browser/ui/exclusive_access/mouse_lock_controller.cc

@@ -29,7 +29,7 @@ const char kMouseLockBubbleReshowsHistogramName[] =
 // The amount of time to disallow repeated pointer lock calls after the user
 // successfully escapes from one lock request.
 constexpr base::TimeDelta kEffectiveUserEscapeDuration =
-    base::TimeDelta::FromMilliseconds(2000);
+    base::TimeDelta::FromMilliseconds(1250);
 
 }  // namespace