GitLab

1) GPU switching is considered and this CL made sure the hardware
   GPU info displayed in the about:gpu is the last active GPU
   before Chrome falls back to SwiftShader.
2) Don't put SwiftShader info into hardware GPU section. Before
   this CL, if we run Chrome with GPU acceleration off, SwiftShader
   ended up in the hardware GPU section.

BUG=1154047
TEST=manual, gpu bots
R=kbr@chromium.org

Change-Id: I08ea41a25d40610e0d13da83f8b5dfeb50011b57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2613741Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#841580}