Disable Activity Log in non-AL browser tests

Some of the API tests generate so many loggable events that the Activity Log needs a really long time to flush, causing test to time out.

http://build.chromium.org/p/chromium.win/builders/Win%20Aura%20Tests%20%283%29/builds/3502/steps/browser_tests/logs/HostSubsets

- Added code to reset command line flags
- Commented out some code in activity_log.cc because extension_service->IsExtensionEnabled is always returning true for an unknown reason

BUG=238256
R=kalman@chromium.org
NOTRY=true

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

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

[felt, 2013-06-10 21:29:55]

ben, please review

[not at google - send to devlin, 2013-06-10 21:33:00]

lgtm wish there was a scoped command line class

[commit-bot: I haz the power, 2013-06-10 21:38:45]

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

[commit-bot: I haz the power, 2013-06-10 23:07:55]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/felt@chromium.org/16759002/9001

[raymes, 2013-06-10 23:13:32]

Committed patchset #4 manually as r205339.

[commit-bot: I haz the power, 2013-06-10 23:31:03]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/felt@chromium.org/16759002/13004

[felt, 2013-06-10 23:32:43]

On 2013/06/10 23:31:03, I haz the power (commit-bot) wrote:
> CQ is trying da patch. Follow status at
> https://chromium-status.appspot.com/cq/felt%40chromium.org/16759002/13004

raymes- is there a problem I need to look at or did it just need a rebase?

[raymes1, 2013-06-10 23:33:54]

On 2013/06/10 23:32:43, felt wrote:
> On 2013/06/10 23:31:03, I haz the power (commit-bot) wrote:
> > CQ is trying da patch. Follow status at
> > https://chromium-status.appspot.com/cq/felt%2540chromium.org/16759002/13004
> 
> raymes- is there a problem I need to look at or did it just need a rebase?

There was a compile failure with the original patch. I fixed it and testing now.

[raymes, 2013-06-10 23:57:31]

Committed patchset #5 manually as r205353.

[benjhayden, 2013-06-11 13:01:53]

Could this CL be related to this bug?
http://crbug.com/248438