Blink>ToolsTest renamed to Blink>Infra

What would this entail? Creating a new test run separate from chromium.webkit?

Note, this bug was filed based on an entry in the Blink Infra roadmap doc (https://docs.google.com/spreadsheets/d/1tO4cfhj_CtX-W8edIl6JD8qf0UWHVJyrzEJOun1I0J4/edit#gid=0).

What this entails, I believe, is adding more builders to chromium.webkit (or chromium.fyi, which are like the builders on chromium.webkit 

I'm not sure, but I think this task could be punted because:
 (1) rebaselines can be done for disabled tests now by un-disabling them, uploading a patch and triggering try jobs, then running webkit-patch rebaseline-cl.
 (2) Flaky tests which have expectations like [ Failure Pass ] are still run, and expectation lines for these flaky tests could be automatically removed from TestExpectations by Tools/Scripts/update-test-expectations if they're passing consistently in recent builds.

So it seems like it's probably not worth it to set up extra builders to run disabled tests.

Ojan, what do you think?

Closing for now for the reasons listed above.