There was a known issue on 4.4 before capped collection deletes were replicated where the contents of a collection could diverge. This can lead to false flag replication constraint violation errors when that node eventually becomes primary on a higher version and tries to delete the documents that don't exist on other nodes anymore

This can only happen on capped collections, so we should add this diagnostic to the log line if the targeted namespace was capped, since that can make it very easy to rule out this as a real issue if the document being deleted is also sufficiently old