* 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

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

Remove special-handling of pre-groups annotations

T88 - Add ability to leave groups

Add a new cancel/leave icon next to private groups
in the groups list and invoke groups.leave() when clicked.

Leaving a group invokes the as-yet-unimplemented
'POST /groups/<id>/leave' endpoint on the server.

T-88

Inline the H icon font

Fix race for session data on startup

The previous fix to use an absolute URL to the icon
font did not work in the Chrome extension because
the base path for assets was different.

The proper solution here will involve refactoring
the CSS build pipeline and possibly automatically
inlining font URLs in the process. I did not just
add a preprocessor to inline all URLs because
that would also have affected fonts in katex.min.css
and added significantly to the size of the CSS bundle.

This commit reverts back to the previous solution of
inlining just the icon font.

See #2571

Several parts of the application require access to the session data
fetched from the server when rendering. On first page load we don't have
this data (something we can fix in the future by inlining the data with
the viewer HTML) and this resulted in a race between the session data
load triggered by `checkAuthentication` (in config/identity.js) and the
query sent to the server by `WidgetController`, which needs to know the
current focused group id.

Fix this by ensuring that the first load of session data is complete
before switching views -- achieved by adding an item to the list of
dependencies passed to `$routeProvider`.

This works, but results in multiple requests for session data in quick
succession, because `checkAuthentication` runs while the view is
loading. To resolve this problem, we add a straightforward TTL check to
the `session.load()` method, and only make a new request if the data is
more than 5m old.

Session data will be overwritten as normal whenever session mutating
methods (`session.login()`, `session.logout()`) etc. are called.

Fixes #2590.

Pulling the server-side template and rendering it with swig is bound to
break if we change the way the form is rendered on the server-side (as I
am in the process of doing).

So, convert this from a sort-of-integrated test to a unit test.

Extract the WebSocket client into its own module and add tests

In preparation for adding additional push notification types,
separate out the client into its own module and add tests.

T-105

Do not show vendored PDF.js in language stats

Group landing pages redesign

 * Implement new look for the Create, Join and Share groups pages.
   The forms are functional without JS but contain a small amount
   of JS logic for enhancements such as selecting the content of
   the share pane.

 * Merge the 'Login to join' and 'Join' pages into a single
   form. The only difference between the two is that
   when the user is not signed in, the button label
   changes from 'Join <Group Name>' to 'Sign in to join <Group Name>'
   which redirects to the login page.

 * Create a new site.scss file which is intended to
   contain only styling for the website and a site-bundle.js
   bundle which contains JS code used only for the site.

 * Extract out the button styles used by <dropdown-menu-btn> into
   a separate .scss file for re-use

 * Add additional colors used by the new group forms
   to variables.scss. To avoid the problems
   with naming that arise when trying to insert additional
   colors into a list with names like 'light', 'lighter' etc.
   I'm starting to use http://chir.ag/projects/name-that-color for
   memorable names.

 * Start to use a '$color-' prefix for colors, in preparation
   for extracting colors into their own file.

Card 93

Re-implement filtering of annotations based on the current selection

44edb50b18f5cd1a78aae32384551c74e6c19304 removed filtering
of annotations when there was a selection alongside other changes.

This re-introduces the check to see whether there is a
selection and if so whether an annotation is in the selected
set when determining whether to show a thread.

Fixes #2553

Implement focus on a group

Fix icon fonts in production builds

The stream page was broken - showing only annotations from the group
that was focused the last time the user was using the sidebar.

Fix it to show annotations from all groups.

When switching between groups (and reloading the angular view more
generally) drafts are persisted. But we don't want to display drafts for
groups other than the one currently focused, because otherwise we'll end
up in a position where we can see annotations published to another
group.

This commit adds an additional condition to
`ThreadController#shouldShow`: if the thread root annotation has a group
set, and that group doesn't match the focused group id, then the thread
will be hidden.