As a first step for user deletion we just deactivate the user.
In the backend the ProfileController class has a new method disable_user
which (if the correct password is given) deactivates the user

In the backend the session/profile factory has a disable_user action
with which the ProfileController can be reached.

We now just listen for changes to the form.$error object rather
than having the controller triggering an error event. This now supports
other changes such as external directives adding validations to
inputs also.

We're only implementing the account form for the moment.

This now directly inlines the template instead of using the Angular
templates. This keeps it consistent with the login tabs. It also
replaces the panels implementation with the Angular tabbable directive.

This will handle whether or not to show the account sheet, it works in
exactly the same way as the login sheet.

This decouples the directive from the rest of the application. It no
longer needs to know how to show the account panel, it just lets the
application know that the user clicked the account button.

This deals with importing templates into the unit tests.

Add more margin between account management sections.

Instead of using the session singleon service, editing the profile
now uses its own angular $resource for backend communication.

With this the directive now really has all the callback handlers.

Also the form validation schema was updated so handle default values
so the backend ProfileController was simplified.

Panel navigation now sits on the topbar. The panels themselves now take up the full width and height of the sidebar.

Account panel tab now has 'active' class.

Panel navigation now sits on the topbar. The panels themselves now take up the full width and height of the sidebar.

Hook the accountmanagement form with the backend.
A user's password or email can be changed using this UI component.

Frontend:
- The accountManagement directive handles submitting the forms
- As the Auth service we use the session service to pack the form data
- The directive has the _answer() and _error() hooks for handling changes
- The backend's message is flashed

Backend:
- horus.views.ProfileController is used
- it has an edit_profile() function which handles both email and password change
- Both edit_profile and changepassword client form is handled by this
- Checks user credentials

Update delete account UI to no longer use window.confirm. Format delete account text and add a confirm password step.

Change forms so that they use the slow validate directive, remove the "nice forms" CSS class and corresponding divs, change name of settingsPanel directive to "panels" and reorganize the code to be a bit more modular and clean. Remove hidden heatmap stuff. Add additional comments

Created settings panel, acount management, and profile directives, along with templates and some basic CSS.

Close #1420

Add the citation back into the annotation card

[no ci]

This fixes #1390. A new controller for the standalone annotation
allows us to determine how to render the annotation and this information
is passed down to the AnnotationController via a combination of scope
properties and attributes.

There are now two distinct states for an annotation, either embedded in
which the annotation is rendered on top of the original document or
standalone, where it appears separately from its document.

Get rid of app_directives.coffee and make it into annotation.coffee
under the directives folder. Put the annotation controller from
controllers.coffee in with it.

Notification email copy and formatting

Simplify the tags input styles

* Simplify the tags, no gradients or drop shadows.
* Use less padding to make them smaller.
* Remove the background color so they adopt the input background. This
  works nicely when the field loses focus.
* Increase the hit area of the delete button. It now takes up the entire
  right side of the tag.

 - PDF: Support latest PDF.js (v1.0.277)
 - TextRange: Handle an error condition

More robust error checking.