Consider rollouts before assigning cohorts (#6138)

Task/Issue URL: https://app.asana.com/1/137249556945/project/1198194956794324/task/1210380290910042?focus=true

### Description
Before assigning any experiment cohort we need to make sure that the feature flag has entered rollout and targets do match, else cohort is not assigned.

### Steps to test this PR
Code review and check end to end tests added.

Alternatively or in addition, do the e2e tests using remote config (json blob etc)

Author: aitorvs

feature-toggles/feature-toggles-api/src/main/java/com/duckduckgo/feature/toggles/api/FeatureToggles.kt

@@ -388,12 +388,9 @@ internal class ToggleImpl constructor(
         val cohortDefaultValue = false
 
         return store.get(key)?.let { state ->
-            // appVersion should be above or equal to minSupportedVersion for the cohort to be assigned
-            // we do not assign a cohort if the feature flag is not enabled remotely
-            val updatedState = if (
-                appVersionProvider.invoke() >= (state.minSupportedVersion ?: 0) &&
-                state.remoteEnableState == true
-            ) {
+            // the feature flag should be "rollout-enabled" before we assign cohorts
+            // this means checking EVERYTHING we check when we call [isEnabled(ANY_COHORT)]
+            val updatedState = if (isRolloutEnabled() == true) {
                 // we assign cohorts if it hasn't been assigned before or if the cohort was removed from the remote config
                 if (state.assignedCohort == null || !state.cohorts.map { it.name }.contains(state.assignedCohort.name)) {
                     state.copy(assignedCohort = assignCohortRandomly(state.cohorts, state.targets)).also {