When the server responds with a State Change Errors from the failCommand failpoint, it should also increase topologyVersion and respond to waiting isMasters. The Drivers team uses failCommand extensively in spec tests for retryable writes+reads. Without this change, it takes the client ~10 seconds (maxAwaitTimeMS) to rediscover the server's state.

For example:

1. client configures a failCommand with NotMaster
2. client runs a retryable write against Primary P
3. client observes a NotMaster error and sets P to Unknown
4. client runs the retry attempt which blocks until P is rediscovered
5. P's Monitor is blocked for 10 seconds waiting for an awaitable isMaster response

After this change to 10 seconds hang should be removed:

1. client configures a failCommand with NotMaster
2. client runs a retryable write against Primary P
3. client observes a NotMaster error and sets P to Unknown
4. client runs the retry attempt which blocks until P is rediscovered
5. P's Monitor immediately receives an awaitable isMaster response and set P to Primary
6. client retry attempt succeeds ASAP