Recommit the generate profile patch

Rebuild test history databases when starting up performance_ui_tests.

[In this reland, manually load the browser dll as a resource on Windows.]

Previously, whenever the theme or history database format were modified, a
large binary database or pak file had to be committed. This was only done
intermittently, messing up some perf expectations. Since last June, this
has added over 100 megabytes to our repository weight.

By generating the SQLite databases and Cached Theme.pak files at startup
of the one test suite that uses them, we're guaranteed that we'll always
be using the current versions and won't add upgrade costs to our
performance_ui_tests. We'll also not continuously add to new binary
resources to the permanent git archive.

BUG=111570
TBR=sky@chromium.org

First Review: https://codereview.chromium.org/14273023

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=200094

[Elliot Glaysher, 2013-05-14 20:48:05]

sky: All the differences are in patchset 2, in the file
chrome/test/perf/perf_ui_test_suite.cc. That code is copied almost verbatim from
other unit tests (in this case, chrome_frame/test/net/fake_external_tab.cc).

Everyone else: TBR/FYI since I already got your lg.

[sky, 2013-05-14 21:12:29]

LGTM

[commit-bot: I haz the power, 2013-05-14 22:42:22]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/erg@chromium.org/14585015/2001

[commit-bot: I haz the power, 2013-05-14 22:42:26]

Can't process patch for file
chrome/test/data/profiles/profile_with_default_theme/Default/History Index
2013-02-journal.
Unexpected git diff output name Index 2013-02-journal
b/chrome/test/data/profiles/profile_with_default_theme/Default/History Index
2013-02-journal.

[Elliot Glaysher, 2013-05-14 22:58:58]

Committed patchset #2 manually as r200094 (presubmit successful).

[Elliot Glaysher, 2013-05-14 23:01:32]

On 2013/05/14 22:58:58, Elliot Glaysher wrote:
> Committed patchset #2 manually as r200094 (presubmit successful).

(Note: Because of the failure both on Windows and the CQ refusing to process the
patch, the change was recreated locally on my linux box and dcommitted there.)