It turns out that emitting ct history can be a meaningful portion of the runtime of sync bootstrap application and they can (temporarily) use almost as much space in the Realm file as the actual live data.

To fix this, we should skip emitting Set instructions on newly created objects, as notifications are the only thing which uses ct history and they don't need to know about mutations on new objects. This will make it so that we produce one instruction per object created rather than one per column per object.