Consider preventing ovewriting new data using the completion tracking tables

[mikix]

We currently have some code that prevents you from overwriting new data with old data by inspecting the meta.lastUpdated field. But Epic doesn't yet provide that field.

So it would be nice if we had an alternate way to avoid that error.

But now that we have completion tracking, which provides the export timestamp of a group... we could do a similar thing and check that the group & resource combo don't have a newer timestamp already. This requires doing some pre-update queries, which is a new thing for the Delta Lake formatter. But it doesn't seem like a crazy query.

This is a breakout issue from #296