The count_plan_summary.js test kills an operation it initiated, and checks that it was interrupted afterwards.
This might fail when running in suites that perform add/remove shard operations in the background.
When draining a shard, an overlapping migration might occur concurrently to the killOp performed by the test.
This can trigger a refresh on the router, making the killed operation being retried instead of being interrupted.

To prevent the failure, we should skip the exit-code check for the interrupted operation, when running in suites that remove shards.