Cover the case where the donor mongod has migration sessions id implemented, but the recipient mongod does not have migration session id implemented. And vice versa.
This will only need to go in the 3.2 branch, where migration session IDs are first introduced, to test 3.2 and 3.0 mongods work correctly during migrations.
- is testing
SERVER-22498 Fix migration session id multiversion failure
- related to
SERVER-20290 Recipient shard for migration can continue on retrieving data even after donor shard aborts