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

One of the pains with working with lazy-rendering platforms
is that events often happen asynchronously.

Now the test suite for two-phased anchoring reflects this
constraint better.

Added tests for two-phase anchoring.

Add a few test cases for Enhanced Anchoring.

API Changes:
 - Introduce the getAnchors() method
 - Make chooseAccessPolicy() public.

Implementation changes:
 - Add the reference pointing to the newly created anchor to
   annotation object right insite the enhanced anchoring plugin,
   instead of in the Monkey code.
 - Fix access to the Annotator class

Added some test cases for EnhancedAnchoring

Restore functionality to toggle the sidebar

Fix reset password exception.

Also removed a couple of unused event handlers.

This clarifies that the method does not actually show/hide the interface
but rather publishes a method across the channel. The host then shows
the frame on response from the sidebar.

Hide activation code input on forgotten password form

Add `ALLOWED_ORIGINS` environment config variable

Open Graph protocol metadata added to Annotation view

Simplify sentry code and catch framework errors

Killed code Markdown button.

Pull annotator out of the sidebar

Conflicts:
	h/static/scripts/controllers.coffee

Keep the AppController away from the root scope and just emit the
lifecycle events for the services. Instantiate AnnotationUIController
with proper injection. Handle digests in the cross-frame service.

Exception handling

Test cleanup.

Eliminate the explicit account module.

This keeps it consistent with the CrossFrame service in the angular
application. Also appropriate as the plugin handles more than just
setting up the bridge.