Remove / deprecate use of now() from SQL insert statements

[dlebauer]

From Scott in terraref/computing-pipeline#174 (comment)

Please don't include the created_at and/or updated_at columns in the insert and update statements! A trigger function handles these automatically so that created_at and updated_at are set to the current time when a row is inserted, and updated_at is reset to the current time when a row is updated. Setting them explicitly overrides this behavior, and using now() sets the column to machine time, not UTC time. (There is a function I defined, utc_now(), which will return UTC time, but you don't need to use it in this case.)

Technically this is a bug, since now() provides local instead of UTC datetime values. However, I am not of any errors this will cause.

This is low priority and a comprehensive update can wait until we transition to dplyr (#395).

[github-actions]

This issue is stale because it has been open 365 days with no activity.