This has been replaced by the `MarkdownView` and `MarkdownEditor`
components.

Convert the editor part of the `<markdown>` component to Preact.

 - Remove the `readOnly` input as this mode is now handled by the
   separate `MarkdownView` component
 - Improve toolbar a11y by:
   - Adding the "toolbar" ARIA role and an aria-label to the toolbar container
   - Using `button` elements for toolbar buttons
   - Increasing the hit target area for buttons
 - Improve toolbar styling by:
   - Using flexbox
   - Using the modern color palette
   - Fixing the padding around the preview output

Convert markdown editor 2/3 - Convert markdown viewer

Convert markdown editor 1/3 - Remove "enabled" state from excerpt component

Convert the view mode of the markdown editor (when `readOnly` is `true`) to Preact.
The edit mode (when `readOnly` is `false`) will become a separate
component.

Simplify the `<excerpt>` component by removing the `enabled` property.
This property was used to avoid the markdown editor being truncated when
rendered inside the excerpt. However it is possible to achieve the same
result without this property by using `ng-if`.

This change will simplify porting the excerpt component to Preact and
also paves the way to splitting the existing `<markdown>` component into
two separate, simpler, components: One for the "view" mode and one for the "edit"
mode.

Bump @sentry/browser from 5.6.3 to 5.7.0

Revert "Improve accessability for toggle buttons"

This reverts commit ab3d902f.

This change caused the client to fail to load on pages where
`window.hypothesisConfig` is not defined.

Bump scroll-into-view from 1.9.7 to 1.11.0

Bump core-js from 2.6.9 to 2.6.10

Bump autoprefixer from 9.6.4 to 9.6.5

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

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

Bumps [@octokit/rest](https://github.com/octokit/rest.js) from 16.33.0 to 16.33.1.
- [Release notes](https://github.com/octokit/rest.js/releases)
- [Commits](https://github.com/octokit/rest.js/compare/v16.33.0...v16.33.1)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [dompurify](https://github.com/cure53/DOMPurify) from 2.0.5 to 2.0.6.
- [Release notes](https://github.com/cure53/DOMPurify/releases)
- [Commits](https://github.com/cure53/DOMPurify/compare/2.0.5...2.0.6)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [scroll-into-view](https://github.com/KoryNunn/scroll-into-view) from 1.9.7 to 1.11.0.
- [Release notes](https://github.com/KoryNunn/scroll-into-view/releases)
- [Changelog](https://github.com/KoryNunn/scroll-into-view/blob/master/CHANGELOG.md)
- [Commits](https://github.com/KoryNunn/scroll-into-view/commits)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [@sentry/browser](https://github.com/getsentry/sentry-javascript) from 5.6.3 to 5.7.0.
- [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.6.3...5.7.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [core-js](https://github.com/zloirock/core-js) from 2.6.9 to 2.6.10.
- [Release notes](https://github.com/zloirock/core-js/releases)
- [Changelog](https://github.com/zloirock/core-js/blob/master/CHANGELOG.md)
- [Commits](https://github.com/zloirock/core-js/compare/v2.6.9...v2.6.10)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bump chance from 1.1.0 to 1.1.3

Bumps [@babel/core](https://github.com/babel/babel) from 7.6.3 to 7.6.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.6.3...v7.6.4)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Enable throttling of concurrent builds

Jenkins CI builds of the client project are prone to failing when many
concurrent builds occur. This often happens when many Dependabot PRs are
submitted at once during a weekly dependency update. These builds
succeed most of the time when retried.

Limiting the number of concurrent builds per executor can be done globally,
but it can also be done on a per-project basis using the
throttle-concurrents [1] plugin. Assign a throttling category to client
builds so that this latter approach can be used.

[1] https://plugins.jenkins.io/throttle-concurrents

Bumps [chance](https://github.com/chancejs/chancejs) from 1.1.0 to 1.1.3.
- [Release notes](https://github.com/chancejs/chancejs/releases)
- [Commits](https://github.com/chancejs/chancejs/commits/1.1.3)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Improve accessability for toggle buttons

- Add aria attribute for show / hide side bar
- Add aria attribute for show / hide highlights
- Fix a bug that prevents the correct class from showing on the highlight icon when highlights are initially disabled

Share Annotations Panel 3 & 4 of 4: Add `ShareAnnotationsPanel` and replace `ShareDialog` with it

- Remove old angular component and supporting modules/files
- Update `hypothesis-app` component
- Update `TopBar` component

- Perform minor refactor on CSS and remove unnecessary rule

Disable verbose Karma logging

This adds a lot of noise to the Jenkins log and we've gotten all the value we
can out of this for tracking down Jenkins CI build failures. What remains is a
period of time between Karma creating the `context.html` iframe where the test
code executes and the scripts in that iframe starting to actually execute.

During this time neither the Karma logs nor Chrome's verbose log provide any
insight into what is going on. Chrome tracing however does, so that's where the
investigation is continuing.