CLI utility to send invitations

Test form-input interaction with form-validate

Since changing the size of button icons in de75319 we can now style
these actions with button markup and the btn-clean class. The last
remnants of .magicontrol go away.

This reverts commit 08d991f066e48c0388ff76ce24a611c1f553a096, reversing
changes made to d488f9c491c0334ee4f46210ba17127df169a9e6.

Mock and test that half of the interaction, and in doing so show that
it's also optional to use the validator with the input.

Scroll to new annotations on creation

Use domain as citation title if no document

Partly a reaction to fce1f2c, which made icons overall smaller.

This is a bad way to address places where what we really want is the
icon as a badge on an element that has text next it. We have special
styles for buttons, but not for other scenarios. Icons should be
resized based on semantic styles for their use rather than globally.

The config blocks should be after the declarations of services, at
least, so that they can decorate services.

If necessary scroll the sidebar to show a newly created annotation (when
the user clicks the new annotation button).

Add unique ids to the <li> elements that contain the annotations, then
on creating a new annotation set the URL fragment to #<id> and scroll to
show the element.

Fixes #2053.

Bump the number of annotations loaded per request to 200

The overhead associated with a single search call is high enough that
loading only 20 annotations at once is too little. In a naive test this
reduces the time take to request about 300 annotations from 5 seconds to
about 800ms (which, IMO, is still far too slow.)

An annotation's document.title is used as the citation when displaying
an annotation. If this is an older annotation that has no document, fall
back to using the domain as the citation title instead.

Fixes #1542

Remove Dockerfile entrypoint

Handle internal server errors in the registration form

Add a test for how the frontend handles an invalid response from the
server when trying to register a user account. This happens if the
server has an uncaught exception.

Merge branch '1755-handle-internal-server-error-in-registration-form' of github.com:hypothesis/h into 1755-handle-internal-server-error-in-registration-form

Conflicts:
	h/static/scripts/account/auth-controller.coffee

Add a frontend test for when the server returns an error response with a
"reason" but no "errors" in the JSON-object response body.

When catching a non-JSON error response from the server, when trying to
register a user.

Hide orphan annotations in the sidebar

This fixes #1755: no error is shown on the client side when an attempt
to register an account receives a 500 Server Error response.

The failure() method in AuthController gets called and tries to do
{errors, reason} = response.data, but this raises a TypeError because
response.data is undefined (because the response didn't have a valid
JSON body), so the client crashes as well.

The fix is to catch this exception on the client side, and show a
generic error to the user.

Improve packaging, bundling and module boilerplate

Prevent negative interactions with module systems present in injected
pages and refactor browserify interactions with angular to increase
CommonJS accessibility / legibility and isolate angular module system
boilerplate.

- Avoid issues due to mis-detected module environments

  - In the injection script, load only Annotator and jQuery in the
    global scope and then both removed with `noConflict()`. Both are
    loaded with browserify-shim, which prevents jQuery from registering
    itself against require.js, if present (fix #2026).

  - Be explicit about registration of common cross-frame components
    (fix #2090).

    - Lift angular glue into app.coffee. Individual components are
      exported as CommonJS modules.

    - Lift Annotator glue into bootstrap.js (renamed hypothesis.js).

- Break up all modules that contained multiple services/directives/etc,
  such as the formHelpers and uiHelpers modules, as well as catch-all
  files like services.coffee and directives.coffee. For a summary of
  these movements see the bottom of this commit message.

- Rename all services, dropping the -service suffix, to match their
  injected names. This is consistent with how directives are being
  treated, and controllers as well (controllers are registered and
  injected done with the "Controller" suffix).

- Move Annotator subclasses into the annotator subdirectory. This
  change avoids having `Annotator.Host` clash with the `host`
  service and makes it easy to glob dependencies in assets.yaml to
  minimally rebuild either the app or the inject.

---

Summary of structural reorganisation. Modules that have been trivially
renamed (from "foo-service" to "foo") are not included in this list:

    controllers:AppController                   app-controller
    controllers:AnnotationUIController          annotation-ui-controller
    controllers:AnnotationViewerController      annotation-viewer-controller
    controllers:ViewerController                widget-controller

    directives:match                            directive/match
    directives:repeatAnim                       directive/repeat-anim
    directives:whenscrolled                     directive/whenscrolled

    directives/thread:pulse                     pulse

    filters:Converter                           filter/converter
    filters:momentFilter                        filter/moment
    filters:personaFilter                       filter/persona
    filters:urlEncodeFilter                     filter/urlencode

    guest                                       annotator/guest
    host                                        annotator/host

    helpers/form-helpers:createFormHelpers      form-respond
    helpers/form-helpers:formInput              directive/form-input
    helpers/form-helpers:formValidate           directive/form-validate
    helpers/string-helpers:createStringHelpers  unicode
    helpers/tag-helpers                         tags
    helpers/time-helpers                        time
    helpers/ui-helpers:tabbable                 directive/tabbable
    helpers/ui-helpers:tabReveal                directive/tab-reveal

    searchfilters:QueryParser                   query-parser
    searchfilters:SearchFilter                  search-filter
    searchfilters:StreamFilter                  stream-filter

    services:DraftProvider                      drafts
    services:ViewFilter                         view-filter
    services:renderFactory                      render

    session/session-service                     session

    streamsearch                                stream-controller

This fixes #1755: no error is shown on the client side when an attempt
to register an account receives a 500 Server Error response.

The failure() method in AuthController gets called and tries to do
{errors, reason} = response.data, but this raises a TypeError because
response.data is undefined (because the response didn't have a valid
JSON body), so the client crashes as well.

The fix is to catch this exception on the client side, and show a
generic error to the user.