CSP: Suppress violation reports for extension resources.

CSP: Suppress violation reports for extension resources.

We should never get to a point where a `chrome-extension:` resource
shows up in the stack trace for a blocked resource. That said, we're
apparently hitting that scenario somewhat often.

This patch at least ensures that our brokenness isn't spamming reporting
endpoints, and revealing the extensions that users have installed to the
site owners.

BUG=524356
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=201969

[Mike West, 2015-09-09 09:08:17]

mkwst@chromium.org changed reviewers:
+ jochen@chromium.org

[Mike West, 2015-09-09 09:08:17]

WDYT, Jochen? It's not clear to me how to write a good test for this, as I've no
idea why we're blocking these in the first place. Followup CL once I understand
the problem?

-mike

[Mike West, 2015-09-09 09:18:18]

https://codereview.chromium.org/1302363004/diff/1/Source/core/frame/csp/Conte...
File Source/core/frame/csp/ContentSecurityPolicy.cpp (right):

https://codereview.chromium.org/1302363004/diff/1/Source/core/frame/csp/Conte...
Source/core/frame/csp/ContentSecurityPolicy.cpp:750: if
(!violationData.sourceFile().isEmpty() &&
SchemeRegistry::schemeShouldBypassContentSecurityPolicy(violationData.sourceFile().protocol())
Ha, I'm an idiot. Pretend that this reads `KURL(ParsedURLString,
violationData.sourceFile()).protocol()` and that there was an extra `)` at the
end of the line. :(

[jochen (gone - plz use gerrit), 2015-09-09 09:28:51]

lgtm

[Mike West, 2015-09-09 09:55:07]

The CQ bit was checked by mkwst@chromium.org

[commit-bot: I haz the power, 2015-09-09 09:55:13]

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

[commit-bot: I haz the power, 2015-09-09 10:50:39]

Committed patchset #2 (id:20001) as
https://src.chromium.org/viewvc/blink?view=rev&revision=201969