Avoid having to watch the user in route controllers at all by resolving
it as a prerequisite of the routes, much like the store bootstrap. The
user may still be ``null`` but it will not be ``undefined``.

For clarity, the $routeChangeStart handler is changed back to a
function, ``cleanupAnnotations``, that is called explicitly from
the user watcher in the ``AppController`` right before the route
reloads.

Set the FF addon version at build time

Towards vanilla annotator

Most of these changes are either syntactic or should not change
behaviour.

This contains only syntactic changes, but it makes it easier to see an
ever-diminishing diff with upstream Annotator.

We monkeypatch BrowserRange as needed in range_monkey.coffee

This is not in upstream and it's not needed any more.

Remove Annotator.Notification.

Move juicy anchoring bits into a plugin of Annotator

Threading events fix and tests

Rather than looping through all threads, use the references property
to find the parent directly. It should be guaranteed to exist since
one cannot reply to something which does not have an id.

Furthermore, when there is no parent reference, the root serves as
the parent. Without considering this, deleting top level annotations
leave stubs in the UI.

Add some tests that the events do what they're supposed to. NB: the
thread method itself should probably be tested.

Import Annotator

Rather than using prebuilt JavaScript in the vendor directory, build the
relevant Annotator plugins from CoffeeScript imported in the previous
commit.

We don't use I18N or provide locale files, so this serves no purpose.

Rather than using a prebuilt vendored Annotator from our fork, this
commit imports the entire forked Annotator source into the h repository.
Our intent is not to maintain this fork within h, but to remove the fork
repository and incrementally move back to dependence on upstream
Annotator.

Introduce Store resource

This makes it explicit that the function is both a constructor and an
angular resource.