[v4.4] Backport skipping RSTL lock in serverStatus

In 5.0, 4.4, and 4.2 the serverStatus command unnecessarily acquires the RSTL lock for producing the results. This can cause issues with FTDC data reporting as it can have empty reporting periods due to waiting for the lock.

To solve this in SERVER-60016 we skip the RSTL lock acquisition. That change should be backported. It also requires backporting part of SERVER-50678 for the skipRSTLLock parameter in GlobalLock.

The backport to 5.0 is already handled by BACKPORT-13878.