Retry on JavaScript execution interruptions in stepdown suites

When a primary steps down, it interrupts all ongoing user operations. If a command is currently executing JavaScript (like an eval or find with $where), its MozJS scope will be marked as killed and return ErrorCodes::Interrupted. This is expected / desired behavior for a stepdown, so the stepdown passthroughs should be resilient to this error code / message combination. The auto_retry_on_network_error.js override should be updated to retry on this response.

This is separate from SERVER-32565, which tracks adding retries on JS engine internal errors, which may not be desired behavior.