Tag Styles

The selectors and markup here could use a cleanup, but at least now
collapsed annotations that have markdown lists and things will still
collapse.

Tags Redux: styling tags

Account Management

Otherwise, this only clears at the appropriate time when triggered
by a scope change, not when triggered by keyup.

The form-input class now has the directive responsible for setting
the error classes. It watches its scope and sets the errors only
if the model is defined or pristine. This guard keeps the error class
from being set until validation passes (when the model becomes defined)
and keeps it from being cleared until the pristine state is reset.

The form-validate directive is now just a controller for form-input to
register with. It sets all fields to dirty and forces a render on
submit.

These mechanisms are better all around than trying to listen for a the
model to be undefined and setting pristine automatically. The model is
undefined whenever validation is failing. There are times when the from
should maybe be cleared but still show errors. Now, it is left up to
other code to set pristine if the form should be reset.

The $setViewValue field wasn't working.

This fixes an issue where logging in, then logging out and opening
the login form will reveal a form with error messages. This is due
to the execution order of events post login.

https://github.com/hypothesis/h/pull/1275#issuecomment-51777983

Now all forms use the profile view name plus "form". For example
the form for the edit_profile view would be editProfileForm. Each
ngModel is namespaced on the scope by the form name. So again this
would be $scope.editProfile. Lastly each field name uses the
corresponding field in the request payload. All fields are camel case.

This should make it far easier in future to read a form and match it
to the http request.

Moved the event handling logic into the AccountManagement controller

Also moved the code out of the directives module and into it's own file.

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.