Now that we have the colliding contents details , we can be less lossy when
replaying contents to another storage.
Prior to this commit, we would not write the batch of contents to the
destination if a collision was detected . Now we keep those out of
the loop if any. Effectively, not writing the colliding hashes to the destination
We still have to decide what to do for the colliding contents... For that, we
still have the logs referencing the colliding contents though (and sentry ).
Note that could be a shared behavior, in a retrying proxy for example?
 Related to D2777