Use only the steady gesture in frame rate tests.

chrome/test/perf/frame_rate/frame_rate_tests.cc

Index: chrome/test/perf/frame_rate/frame_rate_tests.cc
diff --git a/chrome/test/perf/frame_rate/frame_rate_tests.cc b/chrome/test/perf/frame_rate/frame_rate_tests.cc
index f44c0020ba5fe160a4e66f482d36c59f86003185..4f109208d56e561d623f93062ea702f635543e7d 100644
--- a/chrome/test/perf/frame_rate/frame_rate_tests.cc
+++ b/chrome/test/perf/frame_rate/frame_rate_tests.cc
@@ -84,6 +84,9 @@ class FrameRateTest
     if (HasFlag(kUseReferenceBuild))
       UseReferenceBuild();
 
+    // Turn on chrome.Interval to get higher-resolution timestamps on frames.
+    launch_arguments_.AppendSwitch(switches::kEnableBenchmarking);
+
     // UI tests boot up render views starting from about:blank. This causes
     // the renderer to start up thinking it cannot use the GPU. To work
     // around that, and allow the frame rate test to use the GPU, we must