Example output in server status
```
"opWorkingTime" : {
"commands" :

{ "latency" : NumberLong(3000), "ops" : NumberLong(16), "queryableEncryptionLatencyMicros" : NumberLong(0) }

,
"reads" :

{ "latency" : NumberLong(0), "ops" : NumberLong(0), "queryableEncryptionLatencyMicros" : NumberLong(0) }

,
"writes" :

{ "latency" : NumberLong(0), "ops" : NumberLong(0), "queryableEncryptionLatencyMicros" : NumberLong(0) }

,
"transactions" :

{ "latency" : NumberLong(0), "ops" : NumberLong(0), "queryableEncryptionLatencyMicros" : NumberLong(0) }

},
```

Description of Linked Ticket

From isabel.peters@mongodb.com:

Our system on Cloud Intel to dynamically adjust the profilerLevel slowms value for customer clusters uses serverStatus.opLatencies to determine what the slowms value should be set to for collecting slowlogs. I have just learned that the serverStatus.opLatencies will remain based off durationMillis rather than workingMillis in 8.0 which would be a problem for the system to accurately determine the right profiling slowms threshold

Would it be possible to add opLatencies based off workingMillis in the serverStatus response as well?

We may want to consider adding a different serverStatus section rather than changing the meaning of opLatencies.