Repo Inconsistencies due to OAK-3169

[Manfred Baedke]

Hi,

OAK-3169 caused inconsistencies that currently have to be repaired 
manually, even after a patch has been applied. Since lots of customers 
are suffering from this, Andrew Khoury suggested to implement an 
optional auto-repair feature, which logs a warning and removes and 
re-adds mixin:versionable when a broken version history is found (losing 
the version history, of course).
One question would be where to put the repair code, because it's unclear 
to me if there might be multiple locations in the Oak code where an 
exception might be thrown due to the inconsistency.
Any thoughts?
Best regards,
Manfred