When changing the WiredTiger storage engine config string, the database must be quiescent, otherwise it will fail with "system must be quiescent for upgrade or downgrade".

Currently neither the setParameter command nor the code associated with the wiredTigerEngineRuntimeConfig parameter takes the steps such as acquiring a global X lock to quiesce the database. So it's possible that the WT reconfiguration would fail. It would be nice if we can try to take a global lock to quiesce the database before configuring `wiredTigerEngineRuntimeConfig`.