In SERVER-105688, resharding recipient was made to retry on lockTimeout errors since the error does not get retried by default in withAutomaticRetry. Audit the lock acquisitions of internal resharding collections(like the oplog buffer and conflict stash collections, oplog fetcher, applier and txn cloner collections) to verify if the lockTimeout is present. If so, add test coverage to ensure that the error is retryable.