* Move user management to its own controller and views.
* Allow editing of user names.

* Ensure errors are displayed correctly when form submission fails.
* Validate that the lcasid is always a number (don't allow invalid).
* Appease Rubocop.

CSS:
  - Vertically align sortable columns in the middle.
  - Add styling for sortable column buttons, based in part on the W3C
    ARIA APG recommendation / design pattern[1] for sortable columns.
  - Add more padding between column header and sort arrow.

Application Helper:
  - Have the `sortable` helper create the entire <TH/> element.
  - Set the aria-sort property on the <TH/> element.
  - Space between 'Log Out' to fix weird Windows Narrator glitch.

Stack request base model:
  - Add a method for the human-friendly status of the request.
    This helps DRY the views.

Reference card / stack pass request lists:
  - Fix ups, accessibility best practices, etc.

Proxy Borrower admin views:
  - Fix up for `sortable` helper change.

Locales:
  - Add page titles for the pages missing them.

Closes: ADA-270, ADA-271, ADA-272, ADA-273.

[1]: https://www.w3.org/WAI/ARIA/apg/patterns/table/examples/sortable-table/

Instead of having the name edited by site admins, we update it on the
user's log in action from CAS.  This ensures it is always up to date.

This additionally adds a column to the database for the FrameworkUser
ID of who processed the request, so that the updates cascade.

TBD: Migration logic should be added that will search the database for
existing names and replace them with the FrameworkUser ID, so that
updates cascade for these users as well.