In _runWithDbMetadataLockDeadline,prior to resolving ticket SERVER-104292 fixing the BF-37452, we were relying on a DeadlineGuard to push an artificial deadline, i.e., dbMetadataLockMaxTimeMS, and return an  ExceededTimeLimit error if the deadline was exceeded. However, in some test runs, we observed the guard return a MaxTimeMSExpired error instead of the requested ExceededTimeLimit error. We suspect the issue may have to do with the deadline not honouring the requested error code across RPCs. For what is worth, we only observed this failure sporadically on Windows machines.