Blacklist major_version_check.js from sharding_last_stable suite in 3.6

In 3.4, after running split chunk, shards always refresh their metadata, which would cause any command to that shard from the stale mongos to receive a stale config error (which is what happens). In contrast, in 3.6 and up, shards only refresh their metadata if split chunk fails for some reason, which is why major_version_check.js works. We should blacklist this test in the last stable suite.