feat(db): KAM-325: record data change logs with triggers

[passcod]

Changes

• Adds a logs.changes table modelled on the data schema we nailed in the prepper work
  • Lives in the logs schema which is excluded from lean backups but included in full backups
  • Not included in public schema so it doesn't get its own triggers
• Adds a trigger to most tables in public schema to save their changes in that table
• Changes the trigger system to remove the triggers altogether pre-migrations
• Adds a guard to the trigger auto-adder to only add the triggers when the function is available
• Refactor a little to remove code duplication and use better practices (binds vs string interpolation in queries)

A separate PR will create a manual release step upgrade command which copies all the current state of the tables into logs.changes.

• Use the last updated by column name introduced by nassau
• Make sure we're defaulting that to the system user
• Make sure the system user exists
• Use synced time offset (see nassau's work) for the logged_at timestamp
• Sync it
• Mobile doesn't record its own logs but instead that happens on central sync
• Have a session variable or something that can override the last updated by, so that can be used for records that come from mobile and authed context