Start changeStreams at the lastAppliedOpTime not the lastCommittedOpTime

The last committed optime can be behind last applied, so if you pick that as the start time your stream might pick up writes that were done before the stream was established (if the writes were done without write concern)