Make KeystoneGlue less antisocial

Make KeystoneGlue less antisocial.

Remove -clearRecentStatus which really tied KeystoneGlue too closely to
AboutWindowController.  If KeystoneGlue ever wound up with any other clients,
this relationship would have been harmful.  AboutWindowController now
maintains a static variable to handle what -clearRecentStatus had been used
for.

Remove -releaseDefaultKeystoneGlue, which was only intended to be used for
testing, as a workaround for test flake.  The test flake has been removed.

BUG=none
TEST=none

r30215

[TVL, 2009-10-27 16:28:22]

LGTM with question about variable name

http://codereview.chromium.org/333049/diff/1/5
File chrome/browser/cocoa/about_window_controller.mm (right):

http://codereview.chromium.org/333049/diff/1/5#newcode104
Line 104: static BOOL showingInstallFailedStatus = NO;
Would hasShownInstallFailureStatus make more sense?  The code sets this to YES
and keeps it that way even after the window is closed.  The check here in
awakeFromNib is where it is odd with the current name, if the window just awoke,
it isn't showing anything yet, the flag is to help decide what to show.

[Mark Mentovai, 2009-10-27 16:31:43]

thomasvl@chromium.org wrote:
> http://codereview.chromium.org/333049/diff/1/5#newcode104
> Line 104: static BOOL showingInstallFailedStatus = NO;
> Would hasShownInstallFailureStatus make more sense?

That makes it sound like "has an about box ever shown the install
failure status?" but that's not what we're using it for.

How about recentShownInstallFailureStatus?

Mark