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.

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.

Unclear why it's needed, might be used for file:// endpoints...

* Now throw an error if startDiscovery is called twice.
* Throw an error if two server instances message each other.
* Remove the context of the onDiscovery callback.

* Remove the jQuery dependency.
* Pass in window as an argument to the constructor.
* Move defaults off the prototype and onto the constructor fn.

We nullify the default options to ensure that no objects can be shared
between instances and remove the no-op onConnect callback.

This was fixed by 8e1c52f7 and moving bootstrap into app.coffee

The current implementation assumed that the setupAnnotation method
needed to do a large amount of work and so batched the calls. Our
sidebar no-ops this method so we can effectively get rid of the
setup method and batch calls.