Does anyone else who uses ingestion-as-code have a use case with a set of streams that have an incremental update schedule and a full refresh schedule? We're syncing from Salesforce, and our setup has many formula fields, which slowly drift with incremental syncs, so once a week we'd like to full refresh to bring it up to date. The issue I'm running into is that, if I set up 2 connections with different syncing patterns in Airbyte, they'll show up as separate data assets in Dagster. Is there a neat way to coalesce those, or maybe some alternative solution?