The approach of embedding a link tag in the app.html doesn't really give
us a great deal of flexibility. URLs within the application, perhaps as
a result, tend to be created either from baseURI or from the API URL,
called `serviceUrl` in the code.

This commit leaves the <base> tag alone, but:

- replaces the serviceUrl <link> tag with a settings object,
  `window.hypothesis.settings` which is inlined into app.html.
- replaces the serviceUrl angular service with a generic settings
  service.
- renames serviceUrl to apiUrl, to make its purpose more obvious.

T90 top bar refactor

In preparation for implementing the new top-bar
design, extract it into its own directive.

 * Refactor the 'persona' filter into a simple
   function that returns a {username, provider}
   object which IMO makes for more straightforward
   code.

   Several of the test cases which deal with inputs
   not in that form were removed.

   If account IDs are not guaranteed to be in
   the 'acct:<username>@<provider>' form then
   we should be explicit about what is accepted
   and what is returned.

T-90

For consistency use element directives for components
and attribute directives only for directives that
provide some enhancement to an existing UI

T-90

T93 New 'Clear selection' button design

Sort groups server-side

Following discussion on https://github.com/hypothesis/h/pull/2615
it looks like we can ship this for all users.

T-93

This provides a clearer design for the search status
button.

The new design is part of the groups roll-out and
is only shown when the groups feature is enabled.

T-93

The groups are already sorted in a suitable order
by the server, so they do not need to be sorted
again on the client.

In preparation for implementing a new design for the search/selection
status bar, extract it into its own directive.

Don't endlessly re-request features on connectivity issues

If, for whatever reason, the request to fetch features data fails,
simply retry a little later (with a randomised exponential backoff).
This commit uses the [retry module](https://www.npmjs.com/package/retry)
to provide the backoff logic.

N.B. If we fail 10 times (over a period spanning between ~15 and ~30
minutes, using the defaults from the retry module) then we will simply
stop looking for new features data. There's no point burning client CPU
forever in the hope that the server reappears.

Fixes #2547.

UI tweaks for the group creation form

 * Increase the spacing between the label and the group name

 * Disable focus outline for the group name field, since
   the input has no border

 * Disable autocomplete for the group name field, since
   we are prompting for a _new_ name

Convert Chrome extension to Browserify + CommonJS modules

Push notifications of group membership changes

Server-rendered accounts forms

See linked description in GitHub issue.

It is a bit silly that we are running the Chrome extension tests
exclusively in PhantomJS rather than Chrome, but for the moment,
get the existing tests to run using the same getOwnPropertyNames()
shim that is used for the main client app tests.

It is likely that we will want to handle these events differently in
future, so split them into two separate tests.

 * Remove the logic from app-controller.coffee to focus the Public group
   on logout. This is no longer needed as the 'groups' service automatically
   updates the focused group if the previously focused group is removed.

 * Only emit the SESSION_CHANGED event on updates to the session state,
   not the initial app load, since initialization of the view is deferred
   until the session has already been loaded.

   Since the SESSION_CHANGED handler currently reloads the whole view,
   this avoids reloading the view twice on startup.

   Refactoring handling of SESSION_CHANGED to only update the relevant
   app state is left for a future refactoring.

T-105

 * Sort injected parameter names alphabetically for Angular
   services

 * Use imperative names for group events published on the 'user'
   NSQ topic

 * Avoid unnecessary dance with functools.partial() in streamer.py
   to pass the reader's topic to the message handler

This adds a new class of push notification, 'session-change'
which is broadcast to logged-in clients when changes to the user's
state, including the list of groups that they are a member of,
changes.

When the user creates or joins a group, a notification is
added to the event queue with an associated user ID
which is then broadcast via the web socket.

On the client side, the streamer service listens for the new
class of notification and triggers an update of the session
state in response.

When the user leaves a group, this may trigger an implicit change
of focus if the user was a member of the group.

T-105

Remove the 'notification' feature flag

This is deployed and toggled on everywhere, so we can simplify our code
by removing this feature flag.

Let the annotation post button resize to fit its content

Remove the 'streamer' feature flag

Remove the fixed width from the annotation post button
and let the dropdown menu's width adjust to fit its
content rather than being the same width as the button.

To avoid the menu disappearing into the left edge of
the sidebar, the menu has been re-aligned so that
it is centered underneath the button's dropdown arrow.

 * Simplify the styling used to hide the dropdown menu
   to use just the visibility property instead of
   setting pointer events to none, applying a rotation transform
   _and_ setting opacity to 0.

   I'm unclear why the combination of a transform, pointer events
   and opacity was used originally but the dropdown menus
   continue to work with the simplified styling.

T-112

Rather than flashing a message to check the user's email, display a
persistent message on the reset password form if the code has not been
prefilled.

This commit removes all of the client-side code for handling the
following forms:

- registration
- forgot password
- reset password

The login form remains, as it is of course very convenient to be able to
log into Hypothesis from the sidebar.

The code that depended on this scope variable was moved into the
ThreadController in 0e2bd59. It is no longer referenced anywhere.

https://github.com/hypothesis/h/pull/2451#discussion_r41639447

Visually truncate long bodies and quotes

Enable privacy dropdown even when saving an annotation is disabled

Introduces auto-truncation of long bodies and quotes which expand when
you click on a "More" link.

Feature flagged as 'truncate_annotations'.

 * Remove the 'line-height' property from .dropdown-menu-btn that,
   combined with default top/bottom padding for <button> elements
   was causing the button label to be vertically off-center in
   the 'Post to' button.

 * Remove duplication between .primary-action-btn and .dropdown-menu-btn

 * Use $color- variables for palette consistency in .dropdown-menu-btn

T-125

 * Implement design change to allow a user to change the privacy
   setting for an annotation even if the annotation cannot
   yet be published because no tags or text have been entered.

 * Disable the hover state for the main section of the button
   when it is disabled.

T-125

Server-rendered login form

Replace %20 with space when displaying filenames etc