If anchoring an annotation fails to complete within 500ms then assume
that an error occurred during anchoring and that the annotation is
therefore an orphan.

If it later turns out that anchoring just took a long time then the
annotation will simply move from the Orphans tab to the Annotations tab
once anchoring completes.

A timeout within the sidebar app is used rather than relying on the page
code to send back a message if an error occurs during anchoring because
the code that runs in the page context could fail in arbitrary ways due
to interactions with JavaScript on the page.

Remove the 'selection_tabs' feature flag

This is now enabled for all users.

Separate anchored and unanchored annotations into tabs.

Avoid problems due to loss of type information when passing config
options from the page to the sidebar app by serializing the app config
object as a JSON string and then de-serializing it in app.js

When there are no orphans, the Orphans tab is not shown, so we need to
switch back to the Annotations tab in that case.

Refactor some repetition in the functions that produced the counts for
the Annotations, Page Notes and Orphans tabs and extract it into a
separate module where it is easier to test.

Moving this into a single function also makes it easier to memoize
later, so we can avoid recalculating it when the list of annotations has
not changed between two app states.

Default to the annotations tab when user switches between groups, clears a selection or reloads a page.
The ANNOTATIONS_SYNCED event is emitted when annotations for a document have finished anchoring. Because annotations are not marked as orphans until they fail to anchor, select the annotations tab after they have finished anchoring.

Test cases:
-------------
1. On page load localhost:3000
   annotations tab is selected.
   clicking on new note switches to the notes tab with a new draft created.
   switching between tabs maintains tab selection, if notes or annotations.
   when tab selected is orphans, changing groups defaults to the annotations tab.
2. On page load localhost:3000/#annotations:<id>
   clicking on new page note should select the notes tab.
   When an annotation/note is selected, the tab selection carries between group changes.
   all tests listed in #1 above should apply.
3. On page load  localhost:3000/#annotations:<orphan_id>
   clicking on “show all annotations and notes” selects the annotations tab and displays all annotations.
   all tests listed in #1 and #2 above should apply.
   switching between groups selects the annotations tab by default

https://trello.com/c/1NVK2jwv/400-add-a-tab-for-unanchored-annotations
https://trello.com/c/OLdLTlLT/342-separate-annotations-and-notes

Hide orphans tab behind orphans_tab flag.

Fix bug where notes tab isn't selected when user attempts to create a new page note.

Update an annotation's anchoring status and local tag via a Redux action
rather than just direct assignment to the annotation's properties.  This
ensures that store subscribers and a digest cycle happen after the
anchoring status changes. This in turn ensures that the UI state is kept
in sync.

This also brings us another step closer to being able to make annotation
objects immutable within the sidebar app.

Add a service which maps named, parameterized routes to corresponding
URLs on the Hypothesis service.

This makes it easier to identify which URLs the client links to on the
service and update all uses of a particular URL.

Replace "firstRun" config option with "openSidebar" and "openLoginForm"

Update npm-shrinkwrap.json

Embed release version in built package

Fix incorrect usages of the $rootScope

I'm not really sure I understand the mechanism by which this is out of
date or even what the changes here imply, but this is the result of
running

    npm shrinkwrap --dev

with latest npm (3.10.5), and the output appears to be stable --
multiple runs do not change it further.

In addition, installing new packages and rerunning `npm shrinkwrap
--dev` appears to generate a minimal diff after this one-off update.

Rather than relying on the release version being passed in as config,
build the current release version (as read from `package.json`) into the
bundle.

We use browserify-versionify for this, rather than simply requiring
`package.json`, as our current build toolchain does not support any kind
of tree-shaking, so `require('package.json')` would pull the whole of
the `package.json` file into the bundle.

This commit deprecates the confusingly-named "firstRun" embed script
option with two which actually describe the relevant actions triggered.

Unfortunately, at the moment this requires a fairly horrific check that
the string value of a config option is not the literal 'false', due to
the way that the Host code passes configuration from the page frame to
the sidebar frame (using URL query string parameters).

Use shared ESLint config

As described on the trello card:

https://trello.com/c/2NHJkRLa/407-audit-client-for-incorrect-rootscope-usage

there are components or controllers subscribing to events directly on
the root scope via `$rootScope.$on()`. This patch moves those hooks to
the correct `$scope` and causes those events to be `$broadcast` instead
of `$emit` to the root scope.

Fix up indentation using `eslint . --fix`

Use the shared `hypothesis` ESLint config for consistency with our other
projects

* Make the adder a self-contained component

Move adder event handling and UI creation to Adder component, so that
Guest does not need to know about its internal structure or handle
events for it. Instead it just supplies callbacks to invoke when the
Annotate and Highlight buttons are clicked.

This makes it easier to test event handling for the adder and to make
future changes to the UI of the Adder.

This commit removes a piece of logic that stopped propagation of
'mouseup' events from the adder because I couldn't find a clear
explanation in the code or commit history of why that was done.

* Remove a couple of misplaced assertions from tests

Remove assertions checking the horizontal position of the adder in tests
which are only concerned with the vertical position of the adder
relative to the selection.

Fix the "create a free account" link on the sidebar CTA

Avoid double highlighting

When the client is destroyed, it's important that we correctly tear down
the frame-rpc event listeners (bound to the document's `onmessage`
event).

These event listeners are responsible for relaying messages from the
frame-rpc mechanism to various parts of the code on either side of the
frame boundary, including the `AnnotationSync` component. If the
frame-rpc channels aren't correctly torn down, they will hold a
reference to the `Bridge` object, which in turn holds a reference to the
`AnnotationSync` object, and thus old copies of `AnnotationSync` which
should have been garbage-collected will continue to receive events from
the brand new Hypothesis client.

The most visible result of this problem was that repeated activation and
deactivation of the client would result in increasing numbers of
highlights being drawn on annotated text, as reported in
hypothesis/h#3096.

Fixes hypothesis/h#3096.

PhantomJS supports ES5 fully and does not require specific polyfills for
it. This means that we can use exactly the same polyfill script in both
our unit tests and the actual app, which reduces the chances of breakage
due to mismatches.

Additionally, the broken URL constructor could potentially affect other
browsers, so it makes sense to include it in the main polyfill script.

Defer initialization of websocket client until sidebar is interacted with for logged-out users