Revert 89626 - Support automatic javascript test registry in gtest when creating WebUI tests.

Revert 89626 - Support automatic javascript test registry in gtest when creating WebUI tests.

The goal was to support something as simple as the following, where the tests in the
javascript files would be 1st class GTESTs, supporting FLAKY_, DISABLED_, etc, and
registered at linker_initialization time.

WEB_UI_BROWSER_TEST_JS(WebUIBrowserTest, TestJSPass,
                       FILE_PATH_LITERAL("sample_passing.js")) {
  ui_test_utils::NavigateToURL(browser(), GURL(chrome::kChromeUIDownloadsURL));
}

This solution ended up being fairly fragile, and I ended up with a script to parse javascript (with the help of v8_shell) and generate an includable ...-inl.h file with the following for every test in the .js file specified in the |rules| section of tools/js2webui.py

IN_PROC_BROWSER_TEST_F(WebUIBrowserTestPass, testHelper) {
  AddLibrary(FilePath(FILE_PATH_LITERAL("sample_pass.js")));
  ASSERT_TRUE(RunJavascriptTest("testHelper"));
}

http://www.chromium.org/Home/domui-testing

BUG=82437
R=estade@chromium.org,jhawkins@chromium.org
TEST=browser_tests --gtest_filter=WebUIBrowserTest*

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=89453

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=89605

Review URL: http://codereview.chromium.org/7087014

TBR=scr@chromium.org
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=89627