Fix install verification for sideloaded extensions without update urls

Fix install verification for sideloaded extensions without update urls

We found that extensions which are sideloaded via the registry or other
methods that had migrated to the webstore were not being verified
because we weren't even asking the verification service about them.

In order to fix this, this CL moves to an approach where we keep a list
of not verified ids as well as verified ones, and if we encounter an id
that isn't "known bad", we make sure to check with the server first
instead of immediately refusing to load it.

In testing this I also noticed and fixed a case where we were attempting
to disable COMPONENT extensions (it isn't currently possible to disable 
them, but that could change someday so it seemed better not to try 
disabling them or adding them to the list of invalid ids). 

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

[Ken Rockot(use gerrit already), 2014-03-06 22:37:49]

On 2014/03/06 21:48:16, Antony Sargent wrote:

lgtm

[asargent_no_longer_on_chrome, 2014-03-06 22:46:33]

The CQ bit was checked by asargent@chromium.org

[commit-bot: I haz the power, 2014-03-06 22:50:47]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/asargent@chromium.org/189003004/20001

[commit-bot: I haz the power, 2014-03-07 00:34:30]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-03-07 00:34:30]

Try jobs failed on following builders: mac_chromium_compile_dbg

[asargent_no_longer_on_chrome, 2014-03-07 00:42:39]

The CQ bit was checked by asargent@chromium.org

[commit-bot: I haz the power, 2014-03-07 00:46:45]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/asargent@chromium.org/189003004/20001

[commit-bot: I haz the power, 2014-03-07 08:54:39]

Change committed as 255554