Some no-op entries that are important for tracking change streams across a sharded cluster would probably not be written with a tenant ID (e.g. migrateChunkToNewShard). This means that in a Serverless sharded cluster, we wouldn’t be able to track the migration or contraction of a tenant’s collections across the shards on which their slices reside. This ticket is about revisiting this case and making any fixes if required.