Allow the user to create an annotation using the keyboard by selecting
text (using any available method) and pressing the "a" key, or create a
highlight by pressing the "h" key.

The shortcuts are only enabled while the adder toolbar is visible. Since
the toolbar is only shown for static text selections, I think we will be
able to use single keys as the shortcuts without modifiers, and avoid
conflicts with browser and OS shortcuts.

 - `installShortcut` is a function that installs a shortcut key sequence
   listener on the document body (or other user-specified element)
 - `useShortcut` is a hook that installs a shortcut when a component is
   mounted and removes it when the component is unmounted. It can be
   conditionally disabled by setting the shortcut to `null`, since hooks
   themselves cannot be called conditionally

Fix useElementShouldClose to work with Escape key

‘keypress’ is not fired for “Escape” key, so we need to listen for ‘keydown’

Remove unused array utility function

Fix mutation violation when changing focused group

When the focused group is changed, top-level new annotations should
be moved to that newly-focused group, and the newly-focused group should
be persisted as the focused-group default for the user.

Fix mutation violation when changing the focused group: create new
`focus` method in `groups` service; use that to manage the logic of
changing to a new focused group. Remove the `GROUP_FOCUSED` event.
Manage the persisted focused-group default via the `defaults` store
module.

- Fix naming of `$highlight` property
- Add `newPageNote` fixture

Support selecting tabs with the keyboard

Update a couple of variable names as suggested in PR feedback.

 - Add `is` prefix to bool prop
 - Rename `type` to `tabId`

Extract thread-count functions into utility

Fix hidden text for highlights affecting text selection

The hidden "annotation start" and "annotation end" text added before and
after highlights was visually hidden using `opacity: 0` but still
interfered with text selection, presumably because the hidden text was
still "visible" to hit testing. Revise the approach to use the CSS
`clip` instead which avoids this problem.

Fixes https://github.com/hypothesis/support/issues/92

Tab bar buttons responded to mouse/touch press events to make tab
switching feel fast and match how eg. browser tabs behave. However these were not
triggered when activating the buttons using the keyboard. Resolve the
issue by adding the standard click event handler and keeping the
mousedown handler as an optimization.

Also add a missing test for tab selection behavior.

Bump fetch-mock from 9.0.0 to 9.1.1

Bump cross-env from 7.0.0 to 7.0.2

Bump terser from 4.6.4 to 4.6.6

Bump @sentry/browser from 5.13.0 to 5.13.2

Bumps [@babel/preset-env](https://github.com/babel/babel) from 7.8.6 to 7.8.7.
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/master/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/compare/v7.8.6...v7.8.7)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.630.0 to 2.635.0.
- [Release notes](https://github.com/aws/aws-sdk-js/releases)
- [Changelog](https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js/compare/v2.630.0...v2.635.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [eslint-plugin-react](https://github.com/yannickcr/eslint-plugin-react) from 7.18.3 to 7.19.0.
- [Release notes](https://github.com/yannickcr/eslint-plugin-react/releases)
- [Changelog](https://github.com/yannickcr/eslint-plugin-react/blob/master/CHANGELOG.md)
- [Commits](https://github.com/yannickcr/eslint-plugin-react/compare/v7.18.3...v7.19.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [@babel/core](https://github.com/babel/babel) from 7.8.6 to 7.8.7.
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/master/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/compare/v7.8.6...v7.8.7)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [cross-env](https://github.com/kentcdodds/cross-env) from 7.0.0 to 7.0.2.
- [Release notes](https://github.com/kentcdodds/cross-env/releases)
- [Changelog](https://github.com/kentcdodds/cross-env/blob/master/CHANGELOG.md)
- [Commits](https://github.com/kentcdodds/cross-env/compare/v7.0.0...v7.0.2)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [@sentry/browser](https://github.com/getsentry/sentry-javascript) from 5.13.0 to 5.13.2.
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/master/CHANGELOG.md)
- [Commits](https://github.com/getsentry/sentry-javascript/compare/5.13.0...5.13.2)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [terser](https://github.com/terser/terser) from 4.6.4 to 4.6.6.
- [Release notes](https://github.com/terser/terser/releases)
- [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md)
- [Commits](https://github.com/terser/terser/compare/v4.6.4...v4.6.6)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [fetch-mock](https://github.com/wheresrhys/fetch-mock) from 9.0.0 to 9.1.1.
- [Release notes](https://github.com/wheresrhys/fetch-mock/releases)
- [Commits](https://github.com/wheresrhys/fetch-mock/compare/v9.0.0...v9.1.1)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Freeze store state with `immutable` in development builds

Deep-freeze the store state after each action in development builds to
catch accidental mutation bugs such as #1879.

We couldn't do this in the past because the `annotation` component used
to mutate newly created annotations. As a result of recent refactoring,
this no longer happens.

Remove `unloadAnnotations` method from `annotation-mapper`

This method inadvertently (?) mutated annotations in the store which
caused a crash later. Ultimately this method dispatched an event which
was handled only in one place in `root-thread.js` to call
`store.removeAnnotations()`.

This commit removes the method and associated `ANNOTATIONS_UNLOADED`
event and replaces callers with direct calls to
`store.removeAnnotations(...)`.

All uses of Angular events will soon need to be removed as part of the
migration away from Angular JS, but that will happen separately.

Fixes #1879

Bump `eslint-config-hypothesis` and remove redundant `.eslintrc` rule

Upgrade `eslint-config-hypothesis` and remove the local `env` rule that
is handled by it.

Convert "adder" toolbar to Preact

The adder toolbar used to set the `display` style property on its
buttons to resolve an issue with a site that would add `display:none` to
them. The linked issue no longer occurs, possibly because the use of
Shadow DOM hides the buttons from `document.querySelectorAll(...)`.

A timeout that was used to add/remove the `is-active` class from the
toolbar appears to be unnecessary. The "grow and fade in" transition
when the toolbar is shown works without it.

To enable us to take advantage of the UI tooling that we built for the
sidebar app in the "annotator" part of the client (eg. components,
linting, testing infrastructure), we're going to convert UI components
in the "annotator" code over to Preact as well. As a first step, this
commit converts the "adder" toolbar that presents the "Annotate" and
"Highlight" buttons.

 - Extract the logic for creating a shadow DOM root for the adder into
   a separate module (`annotator/util/shadow-root.js`) so we can re-use it for other UI
   elements in future and remove Shadow DOM v0 support since Shadow DOM v1 has
   been available for a long time now.

 - Replace the `adder.html` template file, manual element manipulation
   and manual event listener setup with an `AdderToolbar` Preact
   component (`annotator/components/adder-toolbar.js`), which uses the same
   tooling as components in the sidebar app

In this commit the tests for all the pieces of the adder are covered by
`adder-test.js`. Future commits will split out tests for the individual
pieces.

Replace two dependencies that are only used once