Based on this code, when we return the operation time of a read operation, if the read concern was majority, we return the CurrentCommittedSnapshotOpTime, while if the read concern was anything else (local, linearizable, or snapshot), we returned the lastApplied optime.

For snapshot reads, is this the intended behavior/contract for operationTIme?
We do additionally attach an atClusterTime field in cursor responses. Should the operationTime also be the `atClusterTime`, or is it ok to keep it as the lastApplied?