Repro case with a master build: https://codesandbox.io/s/stoic-mcnulty-dhygf?file=/src/App.js:668-703

Expected: we see content after a second.
Actual: fallback never resolves.

This happens in a sequence of:

1. Normal update
   - which suspends
2. Idle update
   - which also suspends
3. An unrelated normal update immediately followed by a ping (so they're batched)
   - here, we decide to stay on fallback, but should've shown the content

If you remove `_setVersion(v => v + 1);` on line 44 then the issue goes away.
Scheduler.unstable_yieldValue('Foo');
      return (
        <Suspense fallback={<Text text="Loading..." />}>
          {renderContent ? <AsyncText text="A" ms={5000} /> : null}
        </Suspense>
      );
    }
    ReactNoop.render(<Foo />);
    expect(Scheduler).toFlushAndYield(['Foo']);
    ReactNoop.discreteUpdates(() =>
      ReactNoop.render(<Foo renderContent={true} />),
    );
    expect(Scheduler).toFlushAndYieldThrough(['Foo']);
    
    Scheduler.unstable_advanceTime(100);
    await advanceTimers(100);
    expect(Scheduler).toFlushAndYield([
      
      'Suspend! [A]',
      'Loading...',
    ]);
    
    expect(ReactNoop.getChildren()).toEqual([]);
    
    Scheduler.unstable_advanceTime(500);
    jest.advanceTimersByTime(500);