feat: _cq_sync_time for long lived processes

[bbernays]

Which problem is this feature request solving?

Currently for long lived syncing processes like AWS event-based sync, the _cq_sync_time reflects the time that the process began not which is much less meaningful when syncs can last days or weeks.

Describe the solution you'd like

There are a few options:

1. Enable the plugin to set the _cq_sync_time and have the CLI respect that value and not add another column/field
2. Add a _cq_last_updated timestamp value that represents the last time the record was updated. For append mode this column would never be updated, but for update and delete-stale it would be updated every time the record is updated. The Value of the timestamp would either be set by the destination plugin at the time it was added to the batch

Pull request (optional)

• I can submit a pull request