Change collection truncation is performed on both primaries and secondaries. Data is only safe to truncate once the data is consistent up to the maximum timestamp to be truncated. In the case of the primary, this means not truncating after the no oplog hole point (all durable timestamp). On secondaries, it means not truncating past the lastApplied timestamp. 

The changes for this ticket should mirror the safeguards in place for pre-image truncation and be primary/secondary agnostic. 

Old Description:

SERVER-77972 describes a potential issue about holding the PBWM while initializing / truncating CollectionTruncateMarkers. We should investigate the implications of holding the lock for change stream change collection CollectionTruncateMarkers.