Receiving a revision-create events after page-delete events should be dealt as an inconsistency and be processed by the reconciliation job.
This did not work as expected as reported here the entity Q115608572 remained deleted after subsequent edits were made to it after a contributor un-deleted it on 2023-01-12T00:18:53 and subsequent edits happened.
The corresponding page-undelete was not emitted because of T329064 but further edits should have helped to reconstruct this entity in WDQS but this was not the case.
- understand why such inconsistencies are not treated properly
- a revision-create event entering the updater while having a state saying that the entity is deleted should trigger an event in the rdf-streaming-updater.state-inconsistency stream
- the event sent in the rdf-streaming-updater.state-inconsistency should properly trigger an "reconcile" event and restore the entity in WDQS