replayer: Improper replication of the OriginVisitStatus table

when replaying the whole archive, it seems the replayer does (or maybe used to) not handle the origin-visit-status topic properly: it seems to be related to the interaction between creating OriginVisit entries and the related OriginVisitStatus one, especially when there is only one full/partial OriginVisitStatus entry for a given visit. This may happen in the production archive due to the migration from a previous version of the model, before the introduction of the OriginVisitStatus table.

The result of this issue is there are many OriginVisitStatus entries in a replayed storage (a mirror) in the "created" state and no snapshot, while the related entry in the production database is actually in either the "full" or "partial" state with a snapshot entry.