Adjusting Registration updates for managers

In the case where a new user is attempting to sign up, and that user
is a repository manager, the Registration#update action was failing.
This is because `params[:user][:id]` was nil; The
RegistrationController is typically a singular resource (i.e. a
resource in which a given user has one and only one resource, and thus
there is no params[:id] that is passed).

So I am adding some descriptive methods to say what is happening. If
you are not a repository manager we update your account straight away.
If you are a repository manager, we determine if you are updating
another user's account or if you are updating your own account.

This is a stop gap measure as it is rearranging behavior that was
previously moved from Devise into Curate.

Also adjusting how the manager is looked up; By favoring Hash#fetch
over Hash#[], an exception is raised earlier rather than later.
Adjusting registration controller

In the case of a user editing their own account, we need to ask them
to reauthenticate (as the password field is being rendered?).

In the case where I am editing another user's account (i.e. repository
manager), then I am not asking for the password of the account being
edited.
fix key not found error
Merge pull request #508 from projecthydra/feature/218-browse-everything

removing unused js and converting js to coffee script
Merge pull request #507 from projecthydra/fix/user-manager

Adjusting Registration updates for managers
Group should have atleast one editor

HYDRASIR-461
Fixing typo
Merge pull request #509 from projecthydra/feature/461-atleast-one-group-editor

Group should have atleast one editor
Display only works and collections which have open access on profile.

HYDRASIR-425
Merge pull request #510 from projecthydra/feature/425-display-only-public-collections-and-works-on-profile

Display only works and collections which have open access on profile.
Remove associations when a Group/Work is deleted
Merge pull request #511 from projecthydra/feature/implement_call_backs_for_destroy

Remove associations when a Group/Work is deleted