Remove the re-evaluation gap between rollouts

[shell1]

We are being asked more frequently to use Nimbus roll-outs to maintain continuity as features evolve. Using rollouts alone - means there will be up to a 6 hour gap in continuity.

Ex: Fakespot has had a V0, V1, V2, V3, and V4 is coming.

Today there is a gap when we upgrade rollouts - as recipes evaluate new recipes first.

• Users don't qualify for the new rollout - because they are in the old rollout.
• Users look at the old rollout and see that it has ended and unenroll the user.
• • There is up to a 6 hour gap without the feature
• Users evaluate recipes again - enroll in new rollout.

┆Issue is synchronized with this Jira Task