Disable groups drop-down menu when using third-party accounts and there is only one group

Merge branch 'dissable-groups-drop-down' of https://github.com/hypothesis/client into dissable-groups-drop-down

Enable third-party authorities to globally disable annotation share links

`groups` is a list with only one element, but it is still a list not a
single group.

Also fix a typo in a test description.

In the context of the LMS app, the client is embedded inside a Via iframe, which
is inside an LMS app iframe, which is inside Canvas. There is currently no
mechanism in place to propagate the focused annotation down the frame hierarchy.
As a result, share links show up but do not work.

As a simple way to resolve that for an initial version of the LMS app, provide
it with a way to globally disable annotation share links.

In future we may move this responsibility to the "h" service, so that the
availability (or not) of share links is correctly reflected in h API responses.

Part of https://github.com/hypothesis/product-backlog/issues/843

Support recent versions of PDF.js

Recent versions of PDF.js emit a "documentloaded" event when the document
finishes loading. Older versions emit "documentload". Listen for both events to
support both versions.

`PDFViewerApplication.documentFingerprint` was removed in recent
versions of PDF.js [1]. This issue causes loading the bookmarklet into
Firefox 63+ to fail because the client thinks the PDF is still loading.

`PDFViewerApplication.pdfDocument.fingerprint` is the replacement
mentioned in the commit that removed the property and it also appears to
be more clearly a part of PDF.js' documented API.

This change is backwards-compatible with the version of PDF.js that
currently ships with Via.

[1] https://github.com/mozilla/pdf.js/commit/e522b2d87e8eb3d4eb8a391a098a0f6f157e8c12

Use a class which provides a consistent fake PDFViewerApplication
implementation for use by different PDF metadata tests. This will make
it easier to change the fake in order to reflect changes in PDF.js' API,
or the parts of it that we use.

Fix build under Node 11

Upgrade `natives` indirect dependency using method described at
https://github.com/yarnpkg/yarn/issues/4986#issuecomment-395036563.

See also: https://github.com/isaacs/natives/issues/14

- Wrap the clickable logo, group name, and drop down icon in
h2 instead of span and remove aria roll info on div.
- Add display in-line since the focused group is now a
header and by default is block.
- Since the focused group name is now <a> instead of <span>,
the default anchor styling must be overriden.

Use showGroupsMenu to decide when to show drop down

WIP bot configuration

This is an attempt to prevent accidental merging of fixup commits.

See https://github.com/wip/app#configuration

Use atomic git push during release process

Ensure that the release tag is only pushed to GitHub if the release
commit can also be pushed to master.

We are likely to change the release process soon to avoid the need to
push to master at all (see https://github.com/hypothesis/client/issues/810)
but in the meantime this prevents a scenario where:

 - A tag vX.Y.Z gets created
 - The package version is still at X.Y.(Z-1) on master
 - Subsequent builds of master fail because they try and fail to create
   a tag vX.Y.Z which already exists

Disable CoffeeScript support when building sidebar application

All of the modules and tests for the sidebar app that were written in
CoffeeScript have either been removed or converted to JS.

Disable CoffeeScript support when building the sidebar bundle and stop
searching for tests written in CoffeeScript in the src/shared/ and
src/sidebar directories.

Rewrite used parts of stream-filter.coffee in JS

Convert discovery.coffee to JS

Convert shared/discovery tests to JS

Add `make docs` and `make checkdocs`

Add postMessage config delivery example page

Convert viewFilter tests to JS

Deleted the "docs for how to build the docs" since this is now just a
simple `make docs`, as for all our projects.

`setMatchPolicyIncludeAny` no longer exists and is not needed since it
is the _only_ match policy.

This test case reproduces usage of `streamFilter` in
annotation-viewer-content, where the operator is "equals" not "exactly".

Remove support for real-time updates in the /stream view