Clean up Extension Action Handlers Pt 1/2

Clean up Extension Action Handlers Pt 1/2

Combine ManifestHandlers for PageActions and BrowserActions.
Remove support for the uber-deprecated "page_actions" (plural) manifest key.
Clean up related tests.

TBR=avi@chromium.org (c/b/ui/cocoa)
BUG=419475
Committed: https://crrev.com/ba38605aed7c7be61b197bb60ee7c33effdc7dd2
Cr-Commit-Position: refs/heads/master@{#297927}

[Devlin, 2014-10-01 18:51:00]

Patchset #1 (id:1) has been deleted

[Devlin, 2014-10-01 20:16:08]

rdevlin.cronin@chromium.org changed reviewers:
+ yoz@chromium.org

[Yoyo Zhou, 2014-10-02 20:58:18]

LGTM

[Devlin, 2014-10-02 21:07:09]

rdevlin.cronin@chromium.org changed reviewers:
+ avi@chromium.org

[Devlin, 2014-10-02 21:07:19]

The CQ bit was checked by rdevlin.cronin@chromium.org

[commit-bot: I haz the power, 2014-10-02 21:08:14]

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

[commit-bot: I haz the power, 2014-10-02 22:33:20]

Committed patchset #1 (id:20001) as 2af3ab220227e7c5c3d65e627fc6baa69ca833d7

[commit-bot: I haz the power, 2014-10-02 22:34:00]

Patchset 1 (id:??) landed as
https://crrev.com/ba38605aed7c7be61b197bb60ee7c33effdc7dd2
Cr-Commit-Position: refs/heads/master@{#297927}

[tapted, 2014-10-03 00:27:07]

[sheriff] hmm.. could this be the cause of the extension ApiTest failures in
http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%28...
? I have no idea how though.. but this is the only extensiony thing. might be a
debug-build only thing. I think they're crashing. no stacktraces sadly. I'll see
if it's a persistent failure..

[Yoyo Zhou, 2014-10-03 00:53:30]

On 2014/10/03 00:27:07, tapted wrote:
> [sheriff] hmm.. could this be the cause of the extension ApiTest failures in
>
http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%28...
> ? I have no idea how though.. but this is the only extensiony thing. might be
a
> debug-build only thing. I think they're crashing. no stacktraces sadly. I'll
see
> if it's a persistent failure..

Nope. There's a lot more failing there than ApiTests, and they look to be timing
out.