Revert 155218 - Move gpu blacklist to content side.

Revert 155218 - Move gpu blacklist to content side.

http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%282%29/builds/6902/steps/browser_tests/logs/stdio
FAILED (3): GpuFeatureTest.AcceleratedCompositingBlocked
FAILED (5): GpuFeatureTest.WebGLBlocked
FAILED (7): GpuFeatureTest.MultisamplingBlocked
FAILED (9): GpuFeatureTest.Canvas2DBlocked

chrome/test/gpu/gpu_feature_browsertest.cc:343: Failure
Value of: content::GPU_FEATURE_TYPE_ACCELERATED_2D_CANVAS
  Actual: 1
  Expected: type
  Which is: 0
  chrome/test/gpu/gpu_feature_browsertest.cc:133: Failure
  Value of: size_t(0)
    Actual: 0
    Expected: analyzer_->FindEvents(Query::EventName() ==
    Query::String("SwapBuffers"), &events)
    Which is: 3


chrome/test/gpu/gpu_feature_browsertest.cc:290: Failure
Value of: content::GPU_FEATURE_TYPE_MULTISAMPLING
  Actual: 8
  Expected: type
  Which is: 0



When it's on the content side, it can be part of the GpuDataManager, so we don't need to make it a Singleton.

Also, this CL did some cleanup related to this moving.

The main reason for this refactoring is because blacklist is tightly coupled with GpuDataManager.  Putting them on the this side makes it much easier to test the code, and the design is much better.

BUG=
TEST=bots
Review URL: https://chromiumcodereview.appspot.com/10908110

TBR=zmo@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=155223