Improve logging algorithm / report to prevent logging when no changes are made and prevent loss of change log items

Hours should be tracked to Bluebird: http://senatedev.senate.state.ny.us/issues/show/5260

1. User goes to edit screen, doesn't make any changes. Currently a log entry is inserted, but it's empty. We need to suppress log entry when there are no changes.

2 When you save a contact record, the contact row is updated twice - so we group changes by last N seconds. This means that if two edits are done quickly in succession - one of the changes may not be detected. This came up several times in NYSS testing.

3. Allow an external module to suppress the logging aspect on a connection basis. This is primarily used during large imports etc when you want the system to start with a clean slate and start logging from there on out

NOTE: Brian suggested that if we have an algorithm to determine whether there were actually changes made to a record, this would help with both 1 and 2.