The set_schema_version.js test primarily tests 3.4 to 3.6-specific upgrade cases, but it also ensures that all collections have UUIDs on clean startup. This is still necessary to test in master because it is an issue of collections being created prior to setting the featureCompatibilityVersion to 3.6 on clean startup rather than an upgrade/downgrade issue (see SERVER-30131/SERVER-31792). The rest of the UUID checking should be removed and the other parts of the test should be disabled until the featureCompatibilityVersion is bumped.