If you try to login to an unactivated account the error message that the
server returns contains HTML:

You haven't activated your account yet. <strong>Please check your email and
open the link to activate your account</strong>.

Render this client-side as HTML rather than escaping the tags.

Fixes #3501.

In Safari a trailing '#' is appended to URIs extracted from web
documents and PDFs. For URLs this makes no difference as the Hypothesis
search API ignores the fragment identifier. However a URN with a
trailing '#' is considered different from a URN without a trailing '#'.
Since the URI for PDFs is now a URN of the form 'urn:x-pdf:...', when
viewing a PDF in Safari annotations made in other browsers were not
fetched and vice-versa.

The trailing '#' is caused by a bug in the `URL.hash` setter in Safari.

According to section 6.3 of the URL spec [1], setting URL.hash to an empty
string should _remove_ the fragment identifier. In Safari however, it
sets the fragment identifier to an empty string. The result is that when
the URL is serialized, the output is eg. 'urn:x-pdf:aabb#' instead of
'urn:x-pdf:aabb'.

Upstream bug: https://bugs.webkit.org/show_bug.cgi?id=158869
Fixes #3471

[1] https://url.spec.whatwg.org/#urlutils-members

Fix document_uri unique constraint

Rearrange groups views to take advantage of GroupsService

Auto-expand replies for direct-linked annotations

Add a service to manage group creation and membership

Remove unnecessary code for checking type of `annotation.references` field

When direct-linking to an annotation or a reply to one, auto-expand the
annotation thread to make it easier for the user to follow the whole
conversation around it.

 - Convert <simple-search> from CoffeeScript to JS

 - Implement a new set of tests using the createDirective() helper

 - Convert the <simple-search> directive to a modern component-style
   directive which uses one-way bindings and events rather than two-way
   bindings. This makes it consistent with other components in the app.

 - Avoid duplicating the search filter state in multiple places but
   store it only in the Redux store and update it via an action.

The tests for `simple-search` have not been updated in this commit
because they are going to be replaced with a new set using the
`createDirective()` helper in the next commit.

Bugfix: whole page annotation highlights

We now have much more control over how fields are rendered to JSON on
the server and as a result, this field is always either unset or an
array of strings.

Repurposed About panel for Help

Underline links in the Help panel text to make them standout and make
the `/docs/help` URL work when the app is served from browser extensions
extension by prefixing it with the service URL.

Also remove extraneous spaces from around the 'Send us a message' text.

Highlight the specific reply on standalone annotation pages for replies

Reimplement NIPSA operations using NipsaService

Record approximate time-in-queue info for "realtime"

Add some timers to the streamer code

Fixes #3264 with whitespace: no-wrap and flex-shrink: 0

On the standalone pages for replies, indicate the reply which the page
is for by lightening the usernames and bodies of other annotations in the
thread and darkening the username and body of the annotation whose ID
appears in the URL.

Disable a contradictory pep257 rule

Adds hashtag #annotated to web intent

Fix a type error where annotation objects rather than IDs were passed to
the streamer configuration on standalone annotation pages.

When displaying a standalone annotation page for replies, display the
entire conversation thread which that reply is in, including the
original annotation.

Previously standalone annotation pages for replies were broken because
only the reply itself was fetched, the the existence of the top-level
annotation was inferred from the reply's `references` field but because
it was missing, a blank "Message not available" card was shown instead.

Showing the entire thread fixes this problem and also allows the user to
see the complete context of the conversation.

Also refactor the tests to be less tied to the implementation details of
the class and expressed more in terms of what the view does from a
user's point of view.

Fixes #3367

Add a NIPSA service to replace h.nipsa.logic

Allow admins to toggle specific features for a features cohort

`selections()` tried to listen for a 'ready' event on the DOM Document
object. The 'ready' event however is jQuery-specific however so that
never gets triggered.

Instead change the `selections()` function to perform an initial check
for a selection on the next tick and emit a null|DOMRange.

Fixes #3452

Make the styling of quoted snippets of the page consistent with the
styling of block quotes in annotation bodies.

The styling for `<del>` and `<ins>` elements in quotes has been removed
because it is not currently used.

Fixes #3435

Load annotations from DB for /api/search

Set the annotation cursor to a pointer for annotation cards to indicate
that it is clickable (it scrolls the page to that annotation) except for
the body which has a text cursor to indicate that the text is
selectable.

Several places in the <annotation> component assumed that the `tags`
field was an array, as did <tag-editor>. The `tags` and `text` fields
are always set by the server for annotations received from the API but
are not set by Annotator when creating new annotations in the page.

It would be better to initialize all of the required fields for
annotations when they are loaded into the app rather than in the
<annotation> directive. For now however keep the initialization of all
required fields in the same place.

This fixes an error when saving new annotations.

Do not use query property in Feature.{all,remove_old_flags}

Do not use query property in Subscriptions.get_subscriptions_for_uri

Remove query property usage in h.groups