The write_without_shard_key_single_shard_data_placement_change.js fails since it [asserts with a WriteConflict instead of a MigrationConflict (which is what the test expects).
This is because in cases where the range deletion starts on the donor before the findAndModify command, the delete query conflicts with the findAndModify cmd, which in turn uasserts with the WriteConflict error.
The test must be fixed such that the findAndModify command executes before range deletion to ensure we are testing for the MigrationConflict error correctly.