From BF-37598, nodes_dont_prioritize_primary_over_closer_node.js failed because there was an extra sync source change during the set up of the replica set. The test is checking that `serverStatus.syncSource.numSyncSourceChangesDueToSignificantlyCloserNode` is being incremented correctly, but depending on where the value is first checked, it may not account for additional sync source changes properly and cause the test to fail even though the core behavior being tested happens as intended. We should remove testing the metric from this js test and instead add unit test coverage to test that the metric is incremented properly.