Currently run_initial_sync_node_validation.js uses the run_validate_collections script and doesn't pass any options to the validation command, so it uses the default full:true. As seen in BF-38639, this can cause an fassert/EBUSY to be thrown if the oplog applier gets an empty batch during initial sync/startup and attempts to do lock-free reads on a collection that is concurrently being validated. This situation would rarely, if ever, be encountered by a user since it would involve running validation on an active node, so we should change this test hook to use background or non-full validation to prevent this test failure.

Since the situation is possible (though rare) for a user to encounter, I'm filing SERVER-109658 to investigate if concurrency control in the oplog applier should be added for this scenario.