Leveraging the work done in SERVER-29367 to collect the resource utilization of individual tests, we're considering a sharding test to be "resource intensive" if its total io_write in bytes is more than 4 times the median total io_write of all sharding tests. The changes from SERVER-31470 will make it so these tests are run one at a time as part of the sharding*.yml test suites.

• jstests/sharding/auth.js
• jstests/sharding/auto_rebalance_parallel_replica_sets.js
• jstests/sharding/autosplit_heuristics.js
• jstests/sharding/bouncing_count.js
• jstests/sharding/bulk_shard_insert.js
• jstests/sharding/commands_that_write_accept_wc_configRS.js
• jstests/sharding/commands_that_write_accept_wc_shards.js
• jstests/sharding/delete_during_migrate.js
• jstests/sharding/large_chunk.js
• jstests/sharding/migrateBig_balancer.js
• jstests/sharding/move_chunk_wc.js
• jstests/sharding/read_pref.js
• jstests/sharding/read_pref_cmd.js
• jstests/sharding/recovering_slaveok.js
• jstests/sharding/remove2.js
• jstests/sharding/sharding_balance4.js
• jstests/sharding/sharding_migrate_cursor1.js
• jstests/sharding/sharding_rs1.js
• jstests/sharding/stale_mongos_updates_and_removes.js
• jstests/sharding/top_chunk_autosplit.js
• jstests/sharding/zbigMapReduce.js