Issue 87 - Update failed message

[amcghie]

Introduced the ability to audit insert, update, delete and replace operations on the failedMessage collection using the AuditingMongoCollection. By default this is off and can be configured via the following properties:

dao:
  mongo:
    failedMessage:
      audited: true
      auditCollection:
        name: someCollectionAudit

This writes document to the audit collection as follows:

{
    "_id" : ObjectId("5af56fc30b41674d8030c9b0"),
    "auditAction" : "INSERT",
    "auditDateTime" : ISODate("2018-05-11T10:26:11.666Z"),
    "document" : {
        ...
    }
}

A new endpoint (/failed-message/update/{failedMessageId}) has been introduced to allow multiple fields on the FailedMessage object to be updated without needing to submit the original object (see UpdateFailedMessageClient for the API and UpdateFailedMessageComponentTest for example usage).