Fix bug on the isochrone graph creation function
Isochrone frontiers with the same timestamp as the revision being processes need to be invalidated to guarantee that the first occurrence of a blob always ends up in the content-early-in-revision relation. A new test is added that test the case of an incorrectly processed revision leading to inconsistencies.
Migrated from D6829 (view on Phabricator)