As part of the migration away from Angular, replace the use of
angular-mocks for constructing service instances in tests.

 - For tests that only have one or two dependencies, call the service
   constructor directly
 - For tests that have many dependencies, enough that the order could be
   easily mixed up if calling the constructor directly, re-use the
   `Injector` class which is used to wire up services in the real
   application

Several of these tests relied on Angular's built-in `$rootScope`
service. Use of this should go away entirely soon, but for this commit,
just replace it with a minimal mock - either an object with stubs or an
`EventEmitter`.

Reformat with Prettier v2

Even after adjusting the configuration to match Prettier 1.x output as
closely as possible, some breaking changes did require running `make
format`.

Update the configuration so that it matches our other repos and is as
close as possible with Prettier v2.x to Prettier v1.x output.

Add translation map for specific host-config values

add `type-coercion.js` util with 4 methods. These are used on incoming the host-config values `openSidebar` and `requestConfigFromFrame` which may have an incompatible type upstream (via3) from what the client expects.

- toInteger
- toObject
- toString
- toBoolean

These methods coerces specific values into types so that downstream (client) methods can make assumptions. This is part of the prep work to support via3 which will eventually only export strings values in the config.

Bumps [@octokit/rest](https://github.com/octokit/rest.js) from 17.1.1 to 17.1.4.
- [Release notes](https://github.com/octokit/rest.js/releases)
- [Commits](https://github.com/octokit/rest.js/compare/v17.1.1...v17.1.4)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [eslint-plugin-react-hooks](https://github.com/facebook/react/tree/HEAD/packages/eslint-plugin-react-hooks) from 2.5.1 to 3.0.0.
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/master/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/HEAD/packages/eslint-plugin-react-hooks)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.643.0 to 2.648.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.643.0...v2.648.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [prettier](https://github.com/prettier/prettier) from 1.19.1 to 2.0.2.
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/master/CHANGELOG.md)
- [Commits](https://github.com/prettier/prettier/compare/1.19.1...2.0.2)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [@babel/preset-react](https://github.com/babel/babel) from 7.9.1 to 7.9.4.
- [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.9.1...v7.9.4)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Revert mocha to v7.0.1

In mocha >= 7.1.0, exceptions thrown in test hooks (eg. a `beforeEach`
hook) cause the tests to hang without printing any useful exception
details.

From my notes in a Slack investion:

> The karma-mocha package is responsible for running mocha by calling
> mocha.setup() before the test modules are evaluated and then mocha.run()
> after they are evaluated to actually run the tests, as well as listening
> for test events from Mocha’s “runner” and reporting them back to Karma.
> When the beforeEach hook fails, the runner emits a “fail” event which
> karma-mocha receives. karma-mocha then attempts to emit a “test end”
> event and that ends up triggering an exception in a call to
> test.retriedTest() in code which was added in
> https://github.com/mochajs/mocha/pull/4181/files.

Until this issue is resolved, pin mocha to a version that doesn't
trigger this problem.

Replace `annotation-thread` with preact `Thread` component

Adjust CSS not contained within `Thread` to account for annotations
displayed within nested threads.

Exclude src/test-util from code coverage metrics

Our current policy is not to include test-only code in coverage metrics.

Add preStart method to cross-origin-rcp module

When called, allows any incoming rpc request to wait in a queue and be proceeded a short time later when the actual start() method is called. This prevents potential timeouts from incoming RPC requests from LMS (or similar) that arrive after we tipped off the parent frame with a fetchConfig outgoing request but before startServer() is called.

- Rename start() to startServer()
- Use newer module export standard that matches the rest of the app

Remove $location service and annotation subcomponents from sidebar entry module

Remove unused `permissions` service

After `Annotation` was converted to Preact, the subcomponents no longer
need to be wrapped and exposed to Angular.

This built-in Angular service is no longer used, so remove the code to
configure it and expose it to other services.

Use `permissions` util instead

Replace angular `toastr` with preact-compatible toast messages

Replace Angular router

Bump fetch-mock from 9.2.1 to 9.3.1

* preact-compatible
* more accessible

Fix an issue where the route was set before the initial profile and
groups fetch had completed, which could result in the WebSocket
connection being created and then immediately torn down and re-created
on startup.

The route was set too soon because Safari and Chrome emit a "popstate"
event on page load, which triggered a call to `router.sync()` before the
call to `sync()` made by `setupRoute` in src/sidebar/index.js after the
initial profile and groups load.

The solution is to only add the "popstate" listener after the initial
call to `sync()`.

Remove legacy `annotation` component; rename `AnnotationOmega` -> `Annotation`

See https://github.com/hypothesis/client/pull/1906#discussion_r394340280
and https://github.com/hypothesis/client/pull/1906#discussion_r394341565