The test `shard_split_abort_during_upgrade_downgrade.js` has a typo which is an easy fix.

The second test (shard_split_abort_on_setfcv.js) however is failing because the failpoint was previously turned off and we expect to wait on it. The fix for this one is to make sure the `pauseShardSplitAfterBlocking` actually blocks and waits properly.