fix async timers

Author: mdjastrzebski

src/__tests__/suspense-fake-timers.test.tsx

@@ -54,7 +54,7 @@ testGateReact19('resolves timer-controlled promise', async () => {
   expect(screen.queryByTestId('content')).not.toBeOnTheScreen();
   expect(screen.queryByTestId('sibling')).not.toBeOnTheScreen();
 
-  await act(async () => await jest.runOnlyPendingTimersAsync());
+  expect(await screen.findByTestId('content')).toBeOnTheScreen();
   expect(screen.getByTestId('content')).toBeOnTheScreen();
   expect(screen.getByTestId('sibling')).toBeOnTheScreen();
   expect(screen.queryByText('Loading...')).not.toBeOnTheScreen();

src/wait-for.ts

@@ -1,4 +1,5 @@
 /* globals jest */
+import act from './act';
 import { getConfig } from './config';
 import { flushMicroTasks } from './flush-micro-tasks';
 import { copyStackTrace, ErrorWithStack } from './helpers/errors';
@@ -69,7 +70,7 @@ function waitForInternal<T>(
         // third party code that's setting up recursive timers so rapidly that
         // the user's timer's don't get a chance to resolve. So we'll advance
         // by an interval instead. (We have a test for this case).
-        jest.advanceTimersByTime(interval);
+        await act(async () => await jest.advanceTimersByTime(interval));
 
         // It's really important that checkExpectation is run *before* we flush
         // in-flight promises. To be honest, I'm not sure why, and I can't quite