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.

As this channel is outside of the angular framework we need to let it
know that it's internal state may have changed and to re-run it's
watchers.

This fixes some issues where the AppController was still manipulating
the local scope and causing the UI to become out of sync.

i
These also now always set new map instances so that the angular
watcher picks up changes without having to do a deep comparison.

These were the wrong way around.

We need to export them for access in the tests, and we don't really
want them in the global scope (window) so Annotator.Plugin.Guest
seems like a good compromise.

Now consistent with the other cross frame objects in that the optional
"options" object is provided last after required arguments.

There is no need for the called to know what objects are being
instantiated inside the Bridge plugin.

This avoids the confusion of having a property called panel that
refers to an instance of Bridge.

This prevents other objects reaching in and calling methods further
down the chain. If a method needs to be called then it should be
proxied by the Guest object.