All 'tables' as a parameter on the revert api

The revert api reverts the changes associated with a particular change based on the data in the logging tables. It currently calculates a list of tables to revert from. This issue creates the opportunity to pass in a list of tables to revert.

In doing the PR I identified a fatal error under some circumstances - where the contact is not updated it 'touches' the contact record to trigger the triggers to update the modified_date. The triggers are now smarter than they were when that code was done and changing a record with no change no longer triggers an update. However, changing related records does trigger an update - I was able to prove the code is useless and redundant by adding a unit test