Close #1679

Show highlights by default in the Chrome Extension

Only login if not already authenticated

The $error key for the form will have an Array of the errors of its
fields for that key. That means that a bad password response causes
the entire login form to have a truthy $error.response value. That's
not wrong, and we could be using it to show all the errors in a block
at the top of the form, but it's not how we want to use it for this
case.

This allows the page to notify the chrome extension via an "intent"
meta tag that the sidebar should launch in first run mode.

This allows the Chrome extension to be configured with hypothesisConfig.
Also moved this file and the destroy.js file into an extension
subdirectory to avoid confusion with the main app files.

An opening and a closing bracket was lost during the constant
redesign.

Fix #1675

Update annotation card timestamps regulary

Since we use the fuzzyString for the timestamps and
momentjs for the tooltip the date filter was actually
never used.

Code from @nickstenning, introduce the breakpoints array and search
in it for the needed fuzzystring and when to update next instead of
a complex else-if tree.

timeHelpers service has two functions:
- toFuzzyString: returns the fuzzy time string
- nextFuzzyUpdate: returns the next time to update (in sec)

These names were updated in scripts/controllers.coffee but not here.

Calling login here calls identity.request to be called, which in turn
eventually results in the onlogin callback running.

The onlogin callback is not currently idempotent (and it isn't trivial
to make it so) so this results in errors being thrown by Annotator.

Fixes #1611.

Instead of the fuzzyTime filter (and without abusing it)
introducing this service which generates the fuzzyTimeString
(as message) and the next time the fuzzyTimeString should be
updated in seconds (as updateAt) from a given datetime object..

The annotation directive uses the timeHelpers service to get
the fuzzyTimeString and the next time to update.

It wraps the updating with the render service to avoid
the UI update to be flickery and only update when necessary

Fix #1615

Support document access strategy failover

This version supports falling back to the dummy
document access strategy when scanning with d-t-m fails.

(This allows us to create and reanchor annotations with the
selectors and strategies that don't depend on d-t-m functionality.)

This version does not try to recover from scanning
problems, but simply fails early.

Tweaks to Remove bad css classes from buckets

Ability to unsubscribe from notifications

All currently not needed columns were removed: paremeters, query, description
Client generates the description

Many were broken because of the refactoring

The h.auth.local.ProfileController class (which handles account editing)
has now a profile GET call which sends back all subscriptions for an uri
(now a username)

This tab will list the user's notifications.
A new tab is better (even if now it is a one element list) because
works differently then the rest of the account data.

Refactor API code to use annotator-store flaskless

Previously the heatmap tab builder iterates over every tab for each
style that is applied. Now we only perform the iteration once and
apply all updates together.

Once a bucket received a lower or an upper css class, it was never removed.

Once an update function is done, than the bucket with an index of last one - 2
will automatically receive a lower css class because that is the definition
of the isLower function.

The heatmap plugin reuses the already existing buckets and only adds new
ones if neeeded. So after new buckets are added a new one with will get
the lower css class, but nobody removes the lower class from the bucket
which already had it.

Fix adder event handler in Annotator.Guest

This fixes an issue where an exception is raised when the onAdderMouseup
handler tries to call preventDefault on a non-existant event object.

Fix #1648

Update server side templates to use Jinja