Currently DBDirectClient doesn't propagate the read concern used by the parent operation into DBDirectClient.

This can be reproduced by performing a find operation with a $where clause. The command performs a DBDirectClient::find call to the system.js collection. Adding logging statements to get the operation read concern at the beginning of the find command shows this:

[j0:n0] | 2023-05-25T15:28:05.454+00:00 I  QUERY    0       [conn70] "opCtx level comand start","attr":{"readConcern":{"level":"majority","afterClusterTime":{"$timestamp":{"t":1685028485,"i":19}},"provenance":"clientSupplied"}}
...
[j0:n0] | 2023-05-25T15:28:05.507+00:00 I  QUERY    0       [conn70] "opCtx level comand start","attr":{"readConcern":{"provenance":"implicitDefault"}}

This can lead to potentially invalid reads performed by DBDirectClient.