[Feature Request] Finish work around enthistory

[matoszz]

We developed enthistory as a method of programmatically creating history tables which allow us to track any database record which has been changed, updated, or deleted. Additional work is required to finish this implementation but the end-state goal would be:

• You can turn "history" or "auditing" on or off so that these aren't generated if not wanted (especially locally, test environments, etc.)
• There is an ability to have these tables created in an entirely separate database from the one which data is stored in so they can run alongside eachother (and scale over time)
• There are configurations which allow for data to only be retained for a certain period of time
• There is a mechanism that allows for data to be fully purged from both the data tables and the audit tables (the normal behavior is to keep track of data deleted in the underlying schema so that it could be restored from the history tables, but for things such as GDPR we need to be able to fully purge someone's information vs. removing it from the data table and claiming it's deleted but still having a copy in the audit table)
• Data from the history tables can be used for analytics / querying / reporting capabilities
• Permissions implemented the same as the original schema