When visiting a direct-linked annotation (ie. #annotations:<id> is
present in the URL) we want to preserve the selection when the user
signs in, whether the annotation was private or in a group, in which
case they will need to sign in to see it, or public, in which case they
might need to sign in to reply.

Previously public direct-linked annotations became deselected when
signing in because they were unloaded when switching accounts, and this
fired the same ANNOTATION_DELETED event as when an annotation is
removed, which results in the annotation being removed from the
selection.

This commit enables the selection to be preserved by introducing a
different event within the app when annotations are unloaded vs.
deleted. When an annotation is unloaded, it is not removed from the
selection.

Use event constants consistently for events that are emitted
via $rootScope.

Convert AnnotationUI, AnnotationUISync from CoffeeScript to JS

Add Visual Studio Code project config file for JS

Merge pull request #3130 from hypothesis/sheetaluk/303-add-explanation-text-to-the-sharer-on-only-me-and-group-annotations

Add message to private and group annotations sharer.

Use specific Sentry DSN for the client part of H

Fix CSP violation on new homepage

Since we are not allowing inline styles with our CSP policy.

rearranging annotation icons

* Rearrange the annotation action icon positions.
* Add new colours for annotation action button labels.
* Replace icons for reply, edit, delete and share.
* Update style for loggedout users too.
* Update share icon in top-bar.

In combination with JSDoc annotations, this enables IntelliSense,
project navigation, inline documentation, refactoring and other goodies
using Visual Studio Code and other IDEs that integrate with TypeScript's
Language Service for JavaScript (aka.  'Salsa').

See https://code.visualstudio.com/docs/languages/javascript

The project file can be named either `jsconfig.json` without 'allowJs'
or `tsconfig.json` with the 'allowJs' config option enabled. I've opted
for `tsconfig.json` because that turns up better documentation on the
web and is recognized by more tools.

The project config file lives in h/static/scripts so that Visual Studio
only tries to parse and process .js files under that directory.  The
config file does support specifying the set of files to include, but
each file currently has to be listed individually. Glob support is
planned for the future. See
https://github.com/Microsoft/TypeScript/issues/1927

Support filtering test suites to run using '--grep' argument to gulp

Remove user status bitfield

Display message if a direct-linked annotation is not available

The image is specified using the `background-image` property since that
makes it easy to use the same relative URL when the app is served from
the extension and when it is served from the site.

If an annotation is selected but was not successfully loaded,
display a message in the sidebar indicating that the user does
not have permission to see that annotation.

Add support for filtering the tests that are run by Gulp test tasks
using '--grep <pattern>'.

This avoids the need to use the `(describe|it).only` test modifiers to
filter the tests that are run.

The pattern argument is a JS regex expression which is passed directly
to mocha as the 'grep' option.

eg. To start the app test suite in auto-restart mode, but only run tests
for the markdown editor, run:

  gulp test-watch-app --grep markdown

Replace '@p <ident>' with `ident` in JSDoc comments

Using '@p <ident>' to refer to parameters in JSDoc comments is not legal
syntax. Use Markdown backticks instead, ala. Angular's docs.

Switch to appropriate group and scroll to direct linked annotation when sidebar loads

Use more Pythonic way for the argument default value

Refactor feature caching

Change icon size in the bucket bar

Also avoid using `@p` to refer to parameter names in function
documentation, since this isn't valid JSDoc syntax. Use markdown
backticks instead, following conventions in Angular's docs.

The sidebar supports multiple client pages connecting to it
and displaying annotations for all of the connected clients.
As far as I am aware, this functionality is not actually used
anywhere, but this commit fixes an issue where annotations
would be loaded multiple times for some clients if multiple
clients connected.

This was duplicated with varying levels of explanation in several
places.

Although the function is trivial, having it in its own module is useful
for documentation on why it should be used by default.

When the selection is initialized as a result of following
a direct link to an annotation, focus and scroll to the annotation
after it has been successfully fetched from the service.

When the sidebar loads as a result of an '#annotations'
fragment, we do not know which group that annotation is in.

Handle this by first fetching annotations in all groups,
then finding the group containing the selected annotation(s)
and finally filtering the results by that group.

An alternative approach would be to first fetch the
selected annotations in order to determine the group and
then fetching annotations in that group.

This approach however avoids an extra round-trip to the server
in the common case where the total number of annotations across
all groups is less than the default chunk size (200).

widget-controller.js triggers a reload of annotations whenever a
GROUP_FOCUSED event is emitted. Avoid reloading annotations
unnecessarily if group.focus() is called with the currently focused
group.

Extract the logic for paging through search results from
the API into a separate module.

Fix list/quote toolbar command when selection is empty and cursor is at start of line

Improve behavior when the user clicks the toolbar buttons to create a
list or quote and the cursor is positioned at the start of the line with
no selection. In this case, after the command is applied, the cursor
should be positioned ready for the user to start typing the quote or
list.

When the selection is empty and text is inserted at the cursor position,
it is ambiguous whether the selection is 'before' or 'after' the
replaced text. The fix here is to treat the selection as being 'before'
the replaced text.

Fixes #3091

Refactor feature flag to access through Client + caching

Sheetaluk/new sharer

New share dialog enables sharing an annotation on various social media
and a copyable link
https://trello.com/c/9lieEMfd/290-as-a-user-i-can-share-direct-links-to-annotations-with-my-world

* Hide new sharer behind the direct_linking flag
* Update google plus icon