Add a flag to tint GL-composite contents.

In order to debug HW overlay, we need to distinguish between
quads that are directly scanned out and quads that are composited
using GL.

This CL adds a flag to tint all the GL-composited contents to red.
In this way when we can notice when we promote an quad to HW
overlay (it won't be tinted).

Originally we added a similar feature, drawing border on GL composited
quads. That debugging feature caused confusion. The hope is that
this new way of debuggining HW overlays is going to be more intuitive.

Test: tested manually enabling the flag in about://flags.
Bug: 
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: Ifb7b3e90d20d8ada221611c701bda401640123d7
Reviewed-on: https://chromium-review.googlesource.com/810272
Commit-Queue: Daniele Castagna <[email protected]>
Reviewed-by: Avi Drissman <[email protected]>
Reviewed-by: David Reveman <[email protected]>
Reviewed-by: Daniel Cheng <[email protected]>
Cr-Commit-Position: refs/heads/master@{#528415}
diff --git a/chrome/browser/flag_descriptions.h b/chrome/browser/flag_descriptions.h
index c22d15e..06df3d93 100644
--- a/chrome/browser/flag_descriptions.h
+++ b/chrome/browser/flag_descriptions.h
@@ -860,6 +860,9 @@
 extern const char kTcpFastOpenName[];
 extern const char kTcpFastOpenDescription[];
 
+extern const char kTintGlCompositedContentName[];
+extern const char kTintGlCompositedContentDescription[];
+
 extern const char kTopChromeMd[];
 extern const char kTopChromeMdDescription[];
 extern const char kTopChromeMdMaterial[];