Convert `WidgetController` into a `<sidebar-content>` component

Adding auth metrics for login, logout, and signup requested

Adding analytics to share functions

This function is no longer inherited from the parent scope since
`<sidebar-content>` is now a component.

Since this helper function is only used by the sidebar, move it
to the SidebarContentController controller.

Convert 'WidgetController' into a `<sidebar-content>` component which
uses `sidebar_content.html` as a template and convert the route for the
sidebar into a trivial template which just renders this component.

 * Move `widget-controller` to src/sidebar/components/sidebar-content.js

 * Move various helpers for the sidebar content template from the scope
   to the controller, in line with other components.

 * Pass the "auth" and "search" scope properties from the AppController
   instance explicitly to `<sidebar-content>`, since components do not
   inherit scope properties automatically.

Split viewer.html template into one template per app type

Branded sidebar

Convert `<excerpt>` to a component

Reorganize annotation sync tests

Rename all the tests to better reflect what they actually test.

Mostly replacing broadcast local event bus publisher proxying with
"calls function", plus a couple of other clarifications.

Before:

  AnnotationSync
    channel event handlers
      the "deleteAnnotation" event
        ✓ broadcasts the "annotationDeleted" event over the local event bus
        ✓ calls back with a formatted annotation
        ✓ removes an existing entry from the cache before the event is triggered
        ✓ removes the annotation from the cache
      the "loadAnnotations" event
        ✓ publishes the "annotationsLoaded" event
    event handlers
      the "beforeAnnotationCreated" event
        ✓ proxies the event over the bridge
        ✓ returns early if the annotation has a tag

After:

  AnnotationSync
    #constructor
      when "deleteAnnotation" is published
        ✓ calls emit("annotationDeleted")
        ✓ calls the 'deleteAnnotation' event's callback function
        ✓ deletes any existing annotation from its cache before calling emit
        ✓ deletes any existing annotation from its cache
      when "loadAnnotations" is published
        ✓ calls emit("annotationsLoaded")
      when "beforeAnnotationCreated" is emitted
        ✓ calls bridge.call() passing the event
        if the annotation has a $tag
          ✓ does not call bridge.call()

If the tests are grouped according to what class / method / function
they're testing, then it's a lot easier to see what is being tested and
what isn't, and it's easier to find the tests for `foo()` or to know where
to put new tests for `foo()`.

On the other hand when you names tests like
`describe('channel event handlers',` `describe('event handlers',`
`describe('the "loadAnnotations" event',`,
`describe('the "deleteAnnotation" event',` etc then it can be a lot
harder for a reader coming along later to understand how the tests are
organized and how this organization relates to the code itself.

Most of the examples on https://mochajs.org/ use this style of
organizing tests:

    describe('Array', function() {
      describe('#indexOf()', function() {
        it(...
        ...
      });

      describe('#concat()', function () {
        it(...
        ...
      });

      describe('#slice()', function () {
        it(...
        ...
      });

    describe('User', function() {
      describe('#save()', function() {
        it(...

    describe('Connection', function() {
      describe('#find()', function() {
        it(...

This commit reorganizes the AnnotationSync tests along the same lines.

I've also made use of Mocha's `context()` function to group tests
**within a `describe()` for a method** by context. `context()` is just
an alias for `describe()`, but it has different semantics. (This is
also in line with how `context()` is used in the mochajs.org examples).

In the stream and single annotation page it is not possible to select or
focus an annotation since there is no associated page content, so
these callback inputs can be left unset.

The `annotation` component does not declare `isSidebar` or `isLastReply`
in its bindings so these properties are unused.

This is no longer needed since the entire UI is rendered client-side.

In preparation for converting the controllers which provide the logic
for the content area of the sidebar (below the top bar) into components,
split up the viewer.html template into one template for each application
type (sidebar, stream, single annotation page).

This allows removing a number of conditionals from the components in
each template.

Translate AnnotationSync tests to JavaScript

Tidy the CoffeeScript-generated annotation-sync-test.js into something
more human readable.

Just export the `<excerpt>` component definition instead of both the
definition (which includes the controller) and the controller itself.

This module previously lived under `src/sidebar/directive` but it isn't
a directive, only a helper class used by a directive.

Convert `<group-list>` to a component

Just the minimal changes necessary to stop `make lint` from complaining,
while still having `make test` pass.

Some code can be deleted because (eslint informs us) it was unused.

`annotation-sync-test.js` is the unmodified output of
`coffee -bc src/annotator/test/annotation-sync-test.coffee`.

Add a branding directive to bring custom branding to sidebar

Fix annotation ID not being passed to moderation banner correctly.