Earlier, on some versions of PDF.js, we used to
use the PDF.js's FindController as a data source
for the text extraction.

However, at some point, we stopped using the
routines shipped with it, since it didn't always
provide use adequate spacing between the various
pieces of texts. So we ended up just contenating
the various pieces of text ourselves.

Then, for new versions of PDF.js, we introduced
other means of accessing the same information,
completely bypassing the PDFFindController.

This change simply unifies the access; now we can
do the same an all PDF.js versions.

Allow using the API as a virtual root

Add highlight test and change scrolling

... by moving some repeating code into
forEach blocks of the relevant sections.

Fix real-time delete

When receiving a real-time notification about the removal
of an annotation, we emit an annotationDeleted event,
so that all components can react.

Earlier, we emited this event simply with the Annotation
bject that arrived on the wire.

However, some components couldn't deal with this, because
they were expecting to see the 'real' Annotation object,
the ones they already knew about.

So now we do a lookup before emiting the event, and use
the locally found objects instead.

Standardise on userid

This resource request adds a `user_id` query param. But the
corresponding view function doesn't pay any attention to such a
parameter, simply inspecting the authenticated userid to work out whose
profile to provide:

  https://github.com/hypothesis/h/blob/15c39c8b58a8800d7a985c1d29b83fbdb6873266/h/accounts/views.py#L254

Disable extremely slow auto-update of ancient timestamps

When a timestamp is several months old, and we leave
the application around (in a forgotten tab) for
more than three weeks, the usual method of updating
the timestamp fails.

This change works around that by maxing out our timeouts
at 24 days. (This will simply cause us to check the
time in every 24 days.)

Fixes #1952.

I also moved the 5-second minimum to the same time helper.

The goal of this change is to avoid any false appearance
that we are implementing the proposed scrollIntoView() API [1],
while we clearly don't.

So, changes:

 - Rename scrollIntoView to scrollToView
   on both Anchor and Highlight
 - Stop returning promises at both methods

I also updated all the tests to reflect this change.

[1] http://dev.w3.org/csswg/cssom-view/#dom-element-scrollintoview

Load all annotations

To avoid temporary "message not available" cards

Instead of just one search call (with a fix limit),
process the total field from the result of the first
load and while there is still more to load, initiate
a new search query, with the offset property set to
load the remaining ones

Fixes #1948.

Fix class names for the cc font icons

Refactor and fix scrolling - except padding

Small changes here and there

Update copy on password reset forms

Now all copy uses language familiar to those wishing to reset their
password.

This makes the path correct for the rules generated by the icomoon
dashboard.

EnhancedAnchoring plugin:
 - add `getAnchors()` method
 - add `scrollIntoView()` method
 - move some code from the bucket-bar

TextHighlight plugin:
 - get rid of padded scrolling
 - scrollIntoView() no returns a promise

Other:
 - When we click on an annotation card in the sidebar, we need to
   go to the anchor in the document. However, the highlight might
   not exist at this point, so we should look for the Anchor instead.
   So now we call `scrollIntoView()` onthe anchor.
 - The same goes when we click the arrows on the bucket bar
 - Rename `scrollTo` to `scrollIntoView` everywhere.

Switch two-phase anchoring tests to async