Context

In case a {create ... } passes from the createCollectionCoordinator to track a collection, the api check is not performed. This will be fixed in SERVER-92954. Until then, SERVER-92953 introduced a check to skip test cases where the API version is explicitly checked and feature flag "trackUnshardedCollectionUponCreation" is enabled.  (which redirects {create .. } to the createCollectionCoordinator)

Issue

In case the feature flag is disabled, we should skip the test case. However, the suite fcv_upgrade_downgrade_sharding_jscore_passthrough can still randomly enable the feature flag right after the check, but before executing the {create .. } command. That would redirect the create to the createCollectionCoordinator, causing the test to fail. 
This is a known problem, which is usually fixed by disabling the test in case of fcv upgrade/downgrade suites.

note: The test here only checks on the function signature, but forgets to call it. We can fix that on this ticket.