Review logging across mod-agreements

The mod-agreements application log can be quite noisy - especially in relation to the harvesting of data from external KBs.

This level of logging was deliberately introduced to the application to ensure that where there are issues with the external sync it can be easily investigated and resolved. Some of these messages are captured by the application and written to end-user facing log files so that an appropriate member of staff (likely to be a librarian in the first instance) is able to investigate the issue and see what has happened (often the fix will be at a data level either in the remote KB or the local KB in mod-agreements).

We should review the logging in the application, especially in the KB area, to check we are logging at an appropriate level - and if the logging can be reduced (or if it needs to be increased) in specific areas we should do so.