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.
const [show, setShow] = React.useState(false);
      _setShow = setShow;
      return (
        <Suspense fallback="Loading...">
          {show && <AsyncText text="A" />}
        </Suspense>
      );
    }
    await ReactNoop.act(async () => {
      ReactNoop.render(<App />);
    });
    
    await ReactNoop.act(async () => _setShow(true));
    expect(Scheduler).toHaveYielded(['Suspend! [A]']);
    await resolveText('A');
    expect(Scheduler).toHaveYielded(['Promise resolved [A]']);
  });
  it('shows the parent fallback if the inner fallback should be avoided', async () => {
    function Foo({showC}) {