If a change steam is opened on a particular collection with showMigrationEvents:true and a resharding operation happens on another collection, the stream will erroneously report reshardBegin and reshardDoneCatchup events.

This issue does not appear to happen on 5.0, and was likely introduced during the extensive change stream rewrite in PM-1942.