Update rendering.mobile stories to not use timer for control lock

This is a follow-up to: https://chromium-review.googlesource.com/c/chromium/src/+/1696189

There a flag was added which prevents Android from using a timer to lock the
Browser controls on-screen for a minimum amount of time.

This change adds that flag for rendering stories which occur on mobile platforms.

Bug: 896264
Change-Id: I5036ab039ab88a6b6e1acfb604f9e92290ccfc07
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1699696Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#678025}

tools/perf/benchmarks/rendering.py

@@ -74,6 +74,10 @@ class RenderingMobile(perf_benchmark.PerfBenchmark):
   def SetExtraBrowserOptions(self, options):
     options.AppendExtraBrowserArgs('--enable-gpu-benchmarking')
     options.AppendExtraBrowserArgs('--touch-events=enabled')
+    # Disable locking the controls as visible for a minimum duration. This
+    # allows controls to unlock after page load, rather than in the middle of a
+    # story.
+    options.AppendExtraBrowserArgs('--disable-minimum-show-duration')
 
   def CreateCoreTimelineBasedMeasurementOptions(self):
     category_filter = chrome_trace_category_filter.CreateLowOverheadFilter()