Revert of Enable Surfaces on Android (try #3) (patchset #1 id:1 of...

Revert of Enable Surfaces on Android (try #3)  (patchset #1 id:1 of https://codereview.chromium.org/1001203002/)

Reason for revert:
Speculative revert as it seems to be causing a big regression in input_latency/thread_time_cpu_per_frame

BUG=467978

Original issue's description:
> Enable Surfaces on Android (try #3)
>
> The browser compositor contents and renderer contents are each put into separate Surfaces which are aggregated together by a Display.
>
> BUG=449319
>
> Committed: https://crrev.com/8da5f9f03e955304716977004fd4ba1168869aca
> Cr-Commit-Position: refs/heads/master@{#320826}

TBR=sievers@chromium.org,jbauman@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=449319

Review URL: https://codereview.chromium.org/1015813002

Cr-Commit-Position: refs/heads/master@{#320938}

content/browser/gpu/compositor_util.cc

@@ -315,7 +315,7 @@ bool IsThreadedGpuRasterizationEnabled() {
 
 bool UseSurfacesEnabled() {
 #if defined(OS_ANDROID)
-  return true;
+  return false;
 #endif
   bool enabled = false;
 #if (defined(USE_AURA) && !defined(OS_CHROMEOS)) || defined(OS_MACOSX)