Logging indexing failures as audit events (DHH-568)

* logging indexing failures as audit events
* adding paging to audit index
* minor gem updates to handle 2.1.4
I don't think so -- damsolrizer is working with events sent by damsrepo, which doesn't know which user is triggering the events.  So the events only have the ID, action (modify/delete), and a timestamp.