Issue 3225 - Make Diagnostics compatible with the upcoming Adblock Plus 2.7 release

There is a number of changes here:
1) No longer hooking PolicyImplementation.shouldLoad, this functionality moved to a different process and isn`t easily accessible.
2) Because of that, remove the context, document and additional info columns, we no longer have that kind of unprocessed data.
3) Because of that, remove the early returns filter - we can no longer recognize those.
4) Hook Policy.shouldAllow instead of Policy.processNode. The consequences are mostly that we don`t need any additional processing of the parameters, but the return value changes as well.
5) Change the Origin column from a single line to multiple lines, the tooltip should show the entire frame hierarchy. Changed setMultilineContent function to support this.
6) Given that Diagnostics will only work with ABP 2.7 now and not with the older releases, changed the compatibility info to match.

[Wladimir Palant, 2015-12-07 12:17:55]

https://codereview.adblockplus.org/29331940/diff/29331941/chrome/content/watc...
File chrome/content/watcher.js (right):

https://codereview.adblockplus.org/29331940/diff/29331941/chrome/content/watc...
chrome/content/watcher.js:51: notifier = new RequestNotifier(null,
handleFilterHit);
I realized that I didn't test the Filter column - this wasn't actually working.
RequestNotifier no longer supports null as parameter that used to mean "track
all windows." Luckily, using RequestNotifier isn't even necessary - the result
of the shouldAllow call already contains all the hits. So the new patchsets
extracts the filters from this data structure now.

[Thomas Greiner, 2015-12-07 15:24:20]

https://codereview.adblockplus.org/29331940/diff/29332026/chrome/content/watc...
File chrome/content/watcher.js (left):

https://codereview.adblockplus.org/29331940/diff/29332026/chrome/content/watc...
chrome/content/watcher.js:195: entry.cols.type =
String(Policy.localizedDescr[entry.type]);
I know that it is no longer done in the content policy module
(https://codereview.adblockplus.org/29329473/) but was the content type
localization intentionally left behind? Because it wasn't mentioned in the
change notes for this review.

https://codereview.adblockplus.org/29331940/diff/29332026/chrome/content/watc...
File chrome/content/watcher.js (right):

https://codereview.adblockplus.org/29331940/diff/29332026/chrome/content/watc...
chrome/content/watcher.js:29: let currentData = null;
`currentData` is no longer used across multiple functions - only in
`replacementShouldAllow` so we can make it a local variable now.

[Wladimir Palant, 2015-12-07 15:37:55]

https://codereview.adblockplus.org/29331940/diff/29332026/chrome/content/watc...
File chrome/content/watcher.js (left):

https://codereview.adblockplus.org/29331940/diff/29332026/chrome/content/watc...
chrome/content/watcher.js:195: entry.cols.type =
String(Policy.localizedDescr[entry.type]);
On 2015/12/07 15:24:20, Thomas Greiner wrote:
> I know that it is no longer done in the content policy module
> (https://codereview.adblockplus.org/29329473/) but was the content type
> localization intentionally left behind? Because it wasn't mentioned in the
> change notes for this review.

Right, I forgot to mention that. Yes, this was done intentionally - it just
doesn't make much sense to fix that in an English-only internal extension.

https://codereview.adblockplus.org/29331940/diff/29332026/chrome/content/watc...
File chrome/content/watcher.js (right):

https://codereview.adblockplus.org/29331940/diff/29332026/chrome/content/watc...
chrome/content/watcher.js:29: let currentData = null;
On 2015/12/07 15:24:20, Thomas Greiner wrote:
> `currentData` is no longer used across multiple functions - only in
> `replacementShouldAllow` so we can make it a local variable now.

Done.

[Thomas Greiner, 2015-12-07 15:41:55]

LGTM