Problem
SERVER-113022 extended the listcollection to always include the field configDebugDumb for both views and timeseries in case of config db.
The catalog_list_operations_consistency_validator validates listCollections by comparing agaist listCatalog after mapping their fields. 
For multi-version, if listCatalog and listCollections runs against different version the format won't match. 

Fix
We should not run catalog_list_operations_consistency_validator check at all in multi-version. It's normal that in case of mixed binaries the format of the 2 can be temporarily inconsistent. This is not an error. The point of the validity check is to ensure all the fields in listCollections are present to prevent data loss. This is conveniently done by comparing it against listCatalog. The 2 don't really need to match all the time.  Mixed version will inevitably have different formats.

Edit: We opted for just disabling the configDebugDump comparison in multiversion instead of the entire validator. Ideally, new formats should be protected by feature flags and multi-version should therefore not be effected. For this case specifically, the feature flag woundn't work because the listCatalog was working correctly and only listCollection was missing the field. 
We therefore opt to workaround the comparison this time and strip away the configDebugDump field (for comparison) in case of multiVersion. 
I modified the title of the ticket as well