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 [[https://www.wikidata.org/wiki/Wikidata:Report_a_technical_problem/WDQS_and_Search#Coolidge_Auditorium_(Q115608572)_strange_behavior_in_query|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.
AC:
- understand such inconsistencies are not treated properly
- a revision-create event entering the update with a state saying the 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