Fix end-to-end tests

They also need work in DTL since advanceTimersWrapper is now async.

Author: eps1lon

src/__tests__/end-to-end.js

@@ -139,18 +139,14 @@ describe.each([
     test('waitForElementToBeRemoved', async () => {
       await render(<ComponentWithMicrotaskLoader />)
       const loading = () => screen.getByText('Loading..')
-      await waitForElementToBeRemoved(loading)
+      // Already flushed microtasks so we'll never see the loading state in a test.
+      expect(loading).toThrowError(/Unable to find an element with the text/)
       expect(screen.getByTestId('message')).toHaveTextContent(/Hello World/)
     })
 
-    test('waitFor', async () => {
+    test('waitFor is not needed since microtasks are flushed', async () => {
       await render(<ComponentWithMicrotaskLoader />)
-      await waitFor(() => {
-        screen.getByText('Loading..')
-      })
-      await waitFor(() => {
-        screen.getByText(/Loaded this message:/)
-      })
+
       expect(screen.getByTestId('message')).toHaveTextContent(/Hello World/)
     })
 

src/pure.js

@@ -28,6 +28,12 @@ function jestFakeTimersAreEnabled() {
 
 configureDTL({
   unstable_advanceTimersWrapper: cb => {
+    // Only needed to support test environments that enable fake timers after modules are loaded.
+    // React's scheduler will detect fake timers when it's initialized and use them.
+    // So if we change the timers after that, we need to re-initialize the scheduler.
+    // But not every test runner supports module reset.
+    // It's not even clear how modules should be reset in ESM.
+    // So for this brief period we go back to using the act queue.
     return act(cb)
   },
   // We just want to run `waitFor` without IS_REACT_ACT_ENVIRONMENT