Move extensions power API unit test to extensions_unittests

Move extensions power API unit test to extensions_unittests

It was running in Chrome's unit_tests suite for historical reasons.

BUG=397164
TEST=extensions_unittests

Committed: https://crrev.com/30a1ccd6ccf055b61ae86d29657f16513254b773
Cr-Commit-Position: refs/heads/master@{#293946}

[James Cook, 2014-09-09 00:05:39]

jamescook@chromium.org changed reviewers:
+ yoz@chromium.org

[James Cook, 2014-09-09 00:05:40]

yoz, PTAL

derat, just FYI

https://codereview.chromium.org/554963002/diff/1/extensions/browser/extension...
File extensions/browser/extensions_test.h (right):

https://codereview.chromium.org/554963002/diff/1/extensions/browser/extension...
extensions/browser/extensions_test.h:35: // Returned as a BrowserContext since
most users don't need methods from
I've found as I moved tests around that I frequently used browser_context() and
hit compile errors because it didn't know how to cast a TestBrowserContext to a
BrowserContext.  The compiler errors can be a bit hard-to-read in that case.  I
think this pattern for browser_context() vs. extensions_browser_context() make
sense for most users.

[Yoyo Zhou, 2014-09-09 00:43:41]

LGTM

https://codereview.chromium.org/554963002/diff/1/extensions/browser/extension...
File extensions/browser/extensions_test.h (right):

https://codereview.chromium.org/554963002/diff/1/extensions/browser/extension...
extensions/browser/extensions_test.h:35: // Returned as a BrowserContext since
most users don't need methods from
On 2014/09/09 00:05:39, James Cook wrote:
> I've found as I moved tests around that I frequently used browser_context()
and
> hit compile errors because it didn't know how to cast a TestBrowserContext to
a
> BrowserContext.  The compiler errors can be a bit hard-to-read in that case. 
I
> think this pattern for browser_context() vs. extensions_browser_context() make
> sense for most users.

vs. extensions_browser_client, you mean? Yes, I agree.

[James Cook, 2014-09-09 15:23:17]

The CQ bit was checked by jamescook@chromium.org

[commit-bot: I haz the power, 2014-09-09 15:25:00]

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

[commit-bot: I haz the power, 2014-09-09 16:07:42]

Committed patchset #1 (id:1) as b48541746b36366d089cea37401ffcc22ee96a58

[commit-bot: I haz the power, 2014-09-10 03:53:36]

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