Add a workaround for default framebuffer sometimes being SRGB
Add a workaround for default framebuffer sometimes being SRGB

On some GL driver/window system combinations the default framebuffer may
do SRGB conversion, which affects the values written there by draw
operations and read by readPixels. This is known to happen at least on
some Intel systems. For this reason, use an FBO with a known format
instead in the texture end2end tests.

This enables turning on most TextureTest cases on the OpenGL backend.
Tested on Intel HD 4600.

BUG=angleproject:1261
TEST=angle_end2end_tests

Change-Id: I5a39bd1dadf15b7c52793a0f66d67e9f61618b83
Reviewed-on: https://chromium-review.googlesource.com/321612
Reviewed-by: Jamie Madill <7e492b4f1c8458024932de3ba475cbf015424c30@chromium.org>
Reviewed-by: Zhenyao Mo <655bdf1d95ff956cd68886dd9e86ee5e987c9dbb@chromium.org>
Tryjob-Request: Olli Etuaho <38ae6c0e2772a20e8e989f80cb8c99d274e44242@nvidia.com>
Tested-by: Olli Etuaho <38ae6c0e2772a20e8e989f80cb8c99d274e44242@nvidia.com>

ppy/angle,ecoal95/angle,domokit/waterfall,mlfarrell/angle,MSOpenTech/angle,mlfarrell/angle,ppy/angle,domokit/waterfall,ppy/angle,ecoal95/angle,mikolalysenko/angle,ppy/angle,MSOpenTech/angle,mlfarrell/angle,ecoal95/angle,MSOpenTech/angle,ecoal95/angle,mikolalysenko/angle,ecoal95/angle,mikolalysenko/angle,mlfarrell/angle,mikolalysenko/angle,MSOpenTech/angle