Tests which expect to manipulate "REMOVED" nodes must take into account that removing a node will result in a disconnection if the connection is not marked hangUpOnStepDown: false.  This disconnection occurs a few milliseconds after the node is marked "REMOVED", so it's hard to simply take into account.  Best is probably to mark the test client connection with hangUpOnStepDown.

This ticket covers fixing this problem for

force_reconfig_skips_oplog_commitment.js

initial_sync_succeeds_when_syncing_node_removed.js

initial_sync_fails_when_syncing_node_removed.js