Recording input driven frame rate

This CL measures the frame rate in the case when there is input
event and that there is rendering frame associated with that
input event.

We use the existence of swap monitors to indicate whether
there is a rendering frame scheduled due to an input event
that is either handled by the main / impl
thread. We plumb the signal all the way to the
CompositorTimingHistory::DidDraw to record the UMA based on
that info.

Bug: 813183
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I21e51e00cbcb816a7666cdce5b6878835cb6fb68
Reviewed-on: https://chromium-review.googlesource.com/972616
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Brian Anderson <brianderson@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: weiliangc <weiliangc@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562160}

• cc/animation/animation_host.cc[diff]
• cc/animation/animation_host.h[diff]
• cc/scheduler/compositor_timing_history.cc[diff]
• cc/scheduler/compositor_timing_history.h[diff]
• cc/scheduler/compositor_timing_history_unittest.cc[diff]
• cc/scheduler/scheduler.cc[diff]
• cc/scheduler/scheduler.h[diff]
• cc/scheduler/scheduler_unittest.cc[diff]
• cc/trees/layer_tree_host.cc[diff]
• cc/trees/layer_tree_host_impl.cc[diff]
• cc/trees/mutator_host.h[diff]
• cc/trees/proxy_impl.cc[diff]
• cc/trees/proxy_impl.h[diff]
• cc/trees/single_thread_proxy.cc[diff]
• cc/trees/single_thread_proxy.h[diff]
• cc/trees/swap_promise_manager.cc[diff]
• cc/trees/swap_promise_manager.h[diff]
• content/browser/renderer_host/input/input_driven_histogram_browsertest.cc[Added - diff]
• content/test/BUILD.gn[diff]