Suggestion: Process higher priority renders after each useEffect callback

## React Version: 18 ## Steps to Reproduce: Using the classic useDeferredValue demo which shows how an input can be responsive even when components have a slow render, place the delay (loop) in a useEffect callback rather than in the render itself. This can be demonstrated in this [sandbox](https://codesandbox.io/s/quirky-hofstadter-h8yvu1?file=/src/App.js). When you check the box to make the delay in the useEffect rather than the render function the input is no longer responsive. ## Current Behavior The input is not responsive because all useEffect callbacks run to completion before the higher priority render of the input component can occur. ## Expected Behavior The input remains responsive as the high priority render occurs after the completion of each useEffect callback. ## Related While this example is contrived, a real example, where the problem was uncovered, is a fractal application that by necessity does it's canvas processing in a useEffect callback.