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.
});
    
    root.render(<App text="A" shouldSuspend={true} />);
    expect(Scheduler).toFlushAndYield([
      
      'A',
      
      'A',
      'Suspend! [B]',
      'Loading...',
    ]);
    expect(root).toMatchRenderedOutput(<span prop="A" />);
    
    
    ReactNoop.flushDiscreteUpdates();
    
    Scheduler.unstable_advanceTime(2000);
    await advanceTimers(2000);
    expect(root).toMatchRenderedOutput(
      <>
        <span prop="A" />
        <span prop="Loading..." />
      </>,
    );
  });
  
  it('regression: ping at high priority causes update to be dropped', async () => {
    const {useState, useTransition} = React;
    let setTextA;
    function A() {