feat: sync states for webhook sync.complete

[tomkit]

For customers with SyncConfig (and not ConnectionSyncConfig), ObjectSyncs loosely start simultaneously. Using that, we can emit all sync states as part of the sync.complete webhook so they know if other syncs have been finished, which allows them to see if they can process an object that depends on another, e.g., Accounts before Contacts, without storing additional state on their side.

syncedRecordsUpToWatermark is also included for "full then incremental" syncs in the payload so they can process objects up to a specific watermark if needed.

Note: this isn't foolproof, e.g., in situations where the longest sync time runs up against the sync frequency

Test Plan

Tested locally

sync.complete webhook event

...
"related_sync_states": {
    "account": {
      "finished": true,
      "object": "account",
      "object_type": "common",
      "strategy_type": "full then incremental",
      "synced_records_up_to_watermark": 0
    },
    "contact": {
      "finished": true,
      "object": "contact",
      "object_type": "common",
      "strategy_type": "full then incremental",
      "synced_records_up_to_watermark": 1695849081247
    }
  },
  ...

Deployment instructions

[Add any special deployment instructions here]

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
supaglue-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 5, 2023 6:16pm

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
management-ui	⬜️ Ignored (Inspect)	Visit Preview		Dec 5, 2023 6:16pm