In the toggle_feature_compatibility.js FSM workload, setFeatureCompatibilityVersion upgrades can take a long time, because they need to add UUIDs to a large number of collections. As a result, it is very probable for the command to get interrupted more than three times by primary stepdowns. As a result, the setFeatureCompatibilityVersion command gives up retrying, even though it was making forward progress.

There's no failure (if setFeatureCompatibilityVersion kept retrying, it would eventually succeed), and we don't consider this a normal user scenario, so we are just going to remove this test from stepdown suites for now.