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.
<Text text="D" />
      </Suspense>,
    );
    
    expect(Scheduler).toFlushAndYield([
      'A',
      'Suspend! [B]',
      'C',
      'D',
      'Loading...',
    ]);
    
    expect(ReactNoop.getChildren()).toEqual([]);
    
    await resolveText('B');
    
    expect(Scheduler).toHaveYielded(['Promise resolved [B]']);
    expect(Scheduler).toFlushAndYield(['A', 'B', 'C', 'D']);
    expect(ReactNoop.getChildren()).toEqual([
      span('A'),
      span('B'),
      span('C'),
      span('D'),
    ]);
  });
  
  
  
  it('retries on error', async () => {
    class ErrorBoundary extends React.Component {