Remove / reduce archive models and tables

[joecrowley-synergy]

I have read the concerns raised in #122 and I believe there is another option to deal with the issues put forward.

3. Do nothing-ish

This puts the onus of managing audit trails (e.g. the logs) back onto those managing the database and deploying the server. The project could provide suggestions within documentation, (e.g. install the pgAudit extension, or utilise cloud database enhanced logging features), but I feel it is outside the scope of envoy and more of a task to be managed appropriately by those implementing. Thorough auditing itself is unlikely to occur using the archive tables in any case since the values that are contained within are manipulated by the server, open to erroneous data during transfer.

In the few instances where previous values do need to be query-able by the server on a regular basis (e.g. controls), then these could be archived or soft deleted or pure inserted.