Fix up various browser tests not to use WaitForNavigation.

chrome/test/base/ui_test_utils.cc

Index: chrome/test/base/ui_test_utils.cc
diff --git a/chrome/test/base/ui_test_utils.cc b/chrome/test/base/ui_test_utils.cc
index b02d82aecc7e1d59e4158dd6cbcb388edf193572..be65a373fb1505db9b89f87bbd179014a13f6879 100644
--- a/chrome/test/base/ui_test_utils.cc
+++ b/chrome/test/base/ui_test_utils.cc
@@ -57,6 +57,7 @@ namespace ui_test_utils {
 namespace {
 
 // Used to block until a navigation completes.
+// TODO(gbillock): this should be merged with TestNavigationObserver

[Paweł Hajdan Jr., 2011/08/04 17:56:48]

Thanks, and IMHO this is a very high priority. If you have cycles to do that
right after this change, I'd very much appreciate that.

[Greg Billock, 2011/08/11 22:57:45]

Sounds good. I'm planning on a sequence of these as I have some time, and that's
next on the list. Hopefully it'll include some FLAKY unmarking! :-) Is there a
utility we have for running lots of iterations of a test a la blaze test
--runs_per_test?

[Greg Billock, 2011/08/11 22:57:45]

Yeah, I plan on a series of changes, and this is next on the list. Hopefully
some will be to unmark FLAKY. :-) Do we have an analog to blaze test
runs_per_test?

[Paweł Hajdan Jr., 2011/08/11 23:03:02]

You can try --gtest_repeat=-1 --gtest_break_on_failure, but of course that can't
_prove_ a test is not flaky (but can prove that it is).

Anyway, let's focus on removing risky functions primarily. If that allows us to
remove some FLAKY marks, that's great, but isn't my primary concern.

 class NavigationNotificationObserver : public NotificationObserver {
  public:
   NavigationNotificationObserver(const NotificationSource& source,