ChromeOS: use GLFenceEGL, instead of GLFenceARB.
ChromeOS: use GLFenceEGL, instead of GLFenceARB.

GLFenceEGL doesn't require to make GL context current, so it is possible to optimize futher.
Native one-copy and GPU rasterization uses GLFence heavily.

We should pick GL Fence in order:
1- if both EGL_KHR_fence_sync and EGL_KHR_wait_sync are supported, use
GLFenceEGL
2- otherwise, if GL_ARB_sync is supported, use GLFenceARB
3- otherwise, if EGL_KHR_fence_sync is supported (but not EGL_KHR_wait_sync),
use GLFenceEGL (and do client-side waits)
4- otherwise, if GL_APPLE_fence or GL_NV_fence is supported, use
GLFenceAPPLE/GLFenceNV (respectively) and do client-side waits.

BUG=475633

Review-Url: https://codereview.chromium.org/1957343003
Cr-Commit-Position: 972c6d2dc6dd5efdad1377c0d224e03eb8f276f7@{#393221}

axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk,axinging/chromium-crosswalk