In all-feature-flag multiversion testing, in the global_index_rollback.js test the featureFlagGlobalIndexes feature flag is not enabled on the 6.2 nodes which causes the test to fail due to "no such command: '_shardsvrCreateGlobalIndex'".

The above is how this issue was surfaced. We shouldn't run feature flag specific tests during multiversion testing for 2 reasons.

(1) The feature flag c++ code is gated by FeatureFlag::isEnabled(serverGlobalParams.featureCompatibility) & multiversion testing's featureCompatibilityVersion will always be lower than the required FCV for a non-default feature flag. Therefore, the feature flag code can never run with the given FCV. This will always result in failures for featureFlag specific tests.
(2) The previous version is not guaranteed to have the featureFlag feature. So there's a good chance, featureFlag specific tests will fail.

There is a resmoke argument specifically for this use case: --runNoFeatureFlagTests. We should automatically add this when we are running multiversion testing in CI.