Revert of Issue FrameDestructionObserver::frameDestroyed() notification on detach.

Revert of Issue FrameDestructionObserver::frameDestroyed() notification on detach. (patchset #5 id:80001 of https://codereview.chromium.org/881683003/)

Reason for revert:
Linux ChromiumOS Tests (dbg) bot is timing out on ScreenOrientationBrowserTest.CrashTest_UseAfterDetach,

 http://build.chromium.org/p/chromium.webkit/builders/Linux%20ChromiumOS%20Tests%20%28dbg%29%281%29/builds/6186

Can't reproduce locally, but will revert & look into it tomorrow.

Original issue's description:
> Issue FrameDestructionObserver::frameDestroyed() notification on detach.
> 
> Send this notification during detach instead of waiting until finalization,
> which will typically proceed shortly afterwards (non-Oilpan.) The
> supplements of the LocalFrame are cleared at the same time so as to
> prevent FrameDestructionObservers that are also supplements from being
> used in their detached state.
> 
> Doing so makes the observable lifetimes for FrameDestructionObserver's
> frame() identical, with and without Oilpan. Not having GC/finalization
> of frames be observable to scripts is preferable.
> 
> For LocalDOMWindow, a FrameDestructionObserver, its set of registered
> DOMWindowProperty objects are also detached on frameDestroyed(),
> clearing their frame references at the same time.
> 
> R=haraken,dcheng
> BUG=446452
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=189837

TBR=dcheng@chromium.org,haraken@chromium.org,japhet@chromium.org,oilpan-reviews@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=446452
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=189845

[sof, 2015-02-09 22:01:34]

Created Revert of Issue FrameDestructionObserver::frameDestroyed() notification
on detach.

[commit-bot: I haz the power, 2015-02-09 22:02:25]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/908043002/1

[commit-bot: I haz the power, 2015-02-09 22:03:03]

Committed patchset #1 (id:1) as
https://src.chromium.org/viewvc/blink?view=rev&revision=189845

[haraken, 2015-02-10 01:07:30]

LGTM

[Lei Zhang, 2015-02-10 01:22:38]

FWIW, Google Chrome has some internal canary bots that builds against Blink ToT,
and they all hit this problem. So in theory you should be able to repro this on
any of the desktop platforms.

[sof, 2015-02-10 08:33:34]

On 2015/02/10 01:22:38, Lei Zhang wrote:
> FWIW, Google Chrome has some internal canary bots that builds against Blink
ToT,
> and they all hit this problem. So in theory you should be able to repro this
on
> any of the desktop platforms.

Thanks, my apologies for breaking them yet again.

Have now repro'ed the timeout locally; test being adjusted via
https://codereview.chromium.org/909043002/