Identity API: add multi-account support to token cache and request queues

Identity API: add multi-account support to token cache and request queues

This change is part of adding chrome.identity.getAccountAndAuthToken.

The token cache in IdentityAPI and the IdentityMintRequestQueue both had
separate code for tranlating the same API parameters to a lookup key for
their internal maps. They now both use ExtensionTokenKey.

The ExtensionTokenKey includes an account_id field which will allow its
users to support multiple accounts in one profile. All callers currently
use the primary account ID, but will be updated in a future change.

This change also fixes a bug where getAuthToken would return tokens
for the wrong user after switching the account on the profile.

BUG=324874, 322284
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=238292

[Michael Courage, 2013-12-02 19:37:18]

fgorski: please look at everything
jhawkins: OWNERS for chrome/browser/ui/webui

[Michael Courage, 2013-12-02 19:49:05]

-jhawkins (vacation)
+bauerb

[Bernhard Bauer, 2013-12-02 20:22:59]

Web UI LGTM

[fgorski, 2013-12-02 20:54:39]

lgtm

https://codereview.chromium.org/99173004/diff/1/chrome/browser/extensions/api...
File chrome/browser/extensions/api/identity/identity_mint_queue_unittest.cc
(left):

https://codereview.chromium.org/99173004/diff/1/chrome/browser/extensions/api...
chrome/browser/extensions/api/identity/identity_mint_queue_unittest.cc:95:
TEST(IdentityMintQueueTest, ParallelRequestsForDifferentScopes) {
Is that one no longer relevant?

[Michael Courage, 2013-12-02 21:53:06]

https://codereview.chromium.org/99173004/diff/1/chrome/browser/extensions/api...
File chrome/browser/extensions/api/identity/identity_mint_queue_unittest.cc
(left):

https://codereview.chromium.org/99173004/diff/1/chrome/browser/extensions/api...
chrome/browser/extensions/api/identity/identity_mint_queue_unittest.cc:95:
TEST(IdentityMintQueueTest, ParallelRequestsForDifferentScopes) {
On 2013/12/02 20:54:39, Filip Gorski wrote:
> Is that one no longer relevant?

Yes, it was already a little bit redundant, since
ParallelRequestsFromTwoExtensions was there. Now it's extra weird, because it's
really the ExtensionTokenKey's responsibility to make sure the scopes are
handled correctly. From the mint queue's point of view, only the equality
relation of the keys matters; specific fields don't.

[commit-bot: I haz the power, 2013-12-02 22:20:40]

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

[commit-bot: I haz the power, 2013-12-03 03:28:46]

Change committed as 238292