Move DOMActivityLogger and associated code from //chrome to //extensions

Move DOMActivityLogger and associated code from //chrome to //extensions

This is a follow-up to rockot's CL to move extensions::Dispatcher and a
precondition to moving c/r/e/extension_helper.cc.

This was entirely a mechanical move -- no functional changes.

BUG=359836
TEST=compiles

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

[James Cook, 2014-04-30 21:56:42]

kalman, PTAL.  I'll rebase on top of rockot's CL once it lands.

rockot, FYI

[not at google - send to devlin, 2014-04-30 22:00:05]

lgtm I suppose, but what part of extension helper needs this moved?

+devlin FYI.

[Devlin, 2014-04-30 22:05:48]

On 2014/04/30 22:00:05, kalman wrote:
> lgtm I suppose, but what part of extension helper needs this moved?
> 
> +devlin FYI.

Same question as Ben.  Since all the ActivityLogging stuff is part of chrome
(and I don't think it's planning on moving - is that a bad assumption?), this
seems strange.

[Ken Rockot(use gerrit already), 2014-04-30 22:29:22]

On 2014/04/30 22:05:48, D Cronin wrote:
> On 2014/04/30 22:00:05, kalman wrote:
> > lgtm I suppose, but what part of extension helper needs this moved?
> > 
> > +devlin FYI.
> 
> Same question as Ben.  Since all the ActivityLogging stuff is part of chrome
> (and I don't think it's planning on moving - is that a bad assumption?), this
> seems strange.

binding.js depends on APIActivityLogger.

[not at google - send to devlin, 2014-04-30 22:32:43]

On 2014/04/30 22:29:22, Ken Rockot wrote:
> On 2014/04/30 22:05:48, D Cronin wrote:
> > On 2014/04/30 22:00:05, kalman wrote:
> > > lgtm I suppose, but what part of extension helper needs this moved?
> > > 
> > > +devlin FYI.
> > 
> > Same question as Ben.  Since all the ActivityLogging stuff is part of chrome
> > (and I don't think it's planning on moving - is that a bad assumption?),
this
> > seems strange.
> 
> binding.js depends on APIActivityLogger.

ah of course. tricky getting around that in a straightforward way.

[James Cook, 2014-04-30 22:35:08]

On 2014/04/30 22:32:43, kalman wrote:
> On 2014/04/30 22:29:22, Ken Rockot wrote:
> > On 2014/04/30 22:05:48, D Cronin wrote:
> > > On 2014/04/30 22:00:05, kalman wrote:
> > > > lgtm I suppose, but what part of extension helper needs this moved?
> > > > 
> > > > +devlin FYI.
> > > 
> > > Same question as Ben.  Since all the ActivityLogging stuff is part of
chrome
> > > (and I don't think it's planning on moving - is that a bad assumption?),
> this
> > > seems strange.
> > 
> > binding.js depends on APIActivityLogger.
> 
> ah of course. tricky getting around that in a straightforward way.

Sorry, my CL description wasn't very good. ExtensionHelper depends on
UserScriptScheduler (and Ken has already moved UserScriptSlave to //extensions).
 UserScriptScheduler depends on DOMActivityLogger.  And in general the activity
logging code is pretty tightly coupled to the core extensions code, especially
in the renderer.

[James Cook, 2014-05-01 05:06:03]

The CQ bit was checked by jamescook@chromium.org

[commit-bot: I haz the power, 2014-05-01 05:06:45]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jamescook@chromium.org/268553002/1

[commit-bot: I haz the power, 2014-05-01 09:05:47]

Change committed as 267502