Use an object for privacy level models

This makes the association between the level key name and the display
text explicit and tight in the code.

- The permission plugin no longer sets the permissions
- Read permission is a one-item list ["group:__world__"] instead of ["group:__world__", <username>"]
- Privacy directive moved to directives/privacy.coffee
- Uses the simple localStorage solution inside the privacy directive.

When creating a reply, there was an exception
on the console, because the target list is empty,
and some code was not prepared for that.

This takes care of that.

Fix #1661

[WIP] Restore feature to scroll for annotations

Reposition and style show differences checkbox

[WIP] Style the visual diff support

Clicking on an annotation card will bring (one of the) highlights
belonging to that annotation into the view in the document.

Restore visual diff to original behaviour.

... by using ES5 sweetness.

Remove the unnecessary per-target hasDiff flag.

Extract the code for calculating the hasDiff/showDiff flags
into a separate method.

Now there are separate test cases for:
 - A single target with no diff
 - A single target with some diff
 - A single target with some diff, which is case only
 - Multiple targets, some with diffs
 - Multiple targets, some with diffs, but only in case

Furthermore, the used sample diff strings actually look like
real diff strings, for better readibility.

Also, removed some useless lines from the code.

(Thx @aron for all the suggestions.)

Fix holes in message threads

This restores the following corner case:

When there is a difference, but it's only about
the case of the characters, don't want to show
the visual diff by default, but we offer the
feature to the user.

I also updated the tests the reflect the specs.

This will now always keep the branch unless the thread has no
message and no children.

With the messageThread methods. This allows methods to be overridden
by the object itself.

onSetTool calls setVisibleHighlights so this is no longer needed.

- Fix a typo where a closure was unbound
- Always set target.hasDiff rather than having it be sometimes
  undefined and sometimes true.

Thanks @aron

Move the updateTimestamp function into the controller and call it
when render is called. If it is the first time, invoke it with a
flag that causes it to call itself, otherwise it will only update
once.

[WIP] Resurrect the removed visual diff support

Rather than watching a bunch of subproperties, the most complex of
which are the targets, deep watch the whole annotation. The targets
were being deep watched already. This just seems much easier and
clearer than debouncing the render calls, and scales to whatever
properties much change in the future. We'll re-evaluate if this
becomes a bottleneck.

The pattern of comparing the new value passed to a watcher with the old
value is idiomatic angular for avoiding the first digest. Instead, the
first digest is covered by the watch on the model reference identity.
After the initial rendering, the model will not change but the other
properties may, at which point re-rendering will occur.

Calculate the `showDiff` flag for the whole annotation,
instead of on a per-target basis.

Benefits:
 - One less variable stored inside the annotation model
 - We can more easily avoid unwanted overrides of the manually set value.