Remove CallApplyScroll compositing query assert disable

From the comment and linked bug history, this was introduced so that
scroll code could identify main thread scrolling reasons. These have
since moved to the scroll property tree, and no further compositing
queries exist on this codepath (or at least are not hit by tests - this
one is a pretty high-level disablement).

Bug: 1007989, 625676
Change-Id: I86ee8d1ab864fe6334ba4c7c7aa35e07cdc937cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865424
Commit-Queue: Daniel Libby <dlibby@microsoft.com>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#706972}

third_party/blink/renderer/core/dom/node.cc

@@ -607,9 +607,6 @@ void Node::CallDistributeScroll(ScrollState& scroll_state) {
 
 void Node::CallApplyScroll(ScrollState& scroll_state) {
   TRACE_EVENT0("input", "Node::CallApplyScroll");
-  // Hits ASSERTs when trying to determine whether we need to scroll on main
-  // or CC. http://crbug.com/625676.
-  DisableCompositingQueryAsserts disabler;
 
   if (!GetDocument().GetPage()) {
     // We should always have a Page if we're scrolling. See