SERVER-105706Needs Scheduling
Change event's documentKey lacks null/missing values
*Problem* Change streams include a `documentKey` to allow clients to query for individual documents even if multiple shards contain documents with the same _id. The server, though, omits shard key fields from `documentKey` if the document lacks that field. That is: for a collection sharded on (sk: 1, _id: 1), if a document is missing the sk field, its documentKey in the change stream is just (_id: 1 ) rather than (sk: null, _id: 1). Thus, if some other shard contains (sk: 123, _id: 1), a que