This JS test is testing that the primary correctly fasserts during stepdown due to RSTL timeout, but when intent registration is enabled, this test is redundant because there is unit testing that provides the same coverage for this behavior (testing that drain timeout during killConflictingOperations causes an fassert). This ticket is to disable this test when the intent registration feature flag is enabled because it's been noisy on some all_feature_flag variants (see BF-38683) and we have the same test coverage from the intent registration unit tests.