[v13] chore: increase required React et al. versions

Author: mdjastrzebski

package.json

@@ -57,9 +57,9 @@
   },
   "peerDependencies": {
     "jest": ">=28.0.0",
-    "react": ">=18.2.0",
-    "react-native": ">=0.73",
-    "react-test-renderer": ">=18.2.0"
+    "react": ">=18.3.0",
+    "react-native": ">=0.75",
+    "react-test-renderer": ">=18.3.0"
   },
   "peerDependenciesMeta": {
     "jest": {

website/docs/12.x/docs/api/misc/async.mdx

@@ -53,12 +53,6 @@ Avoiding side effects in `expectation` callback can be partially enforced with t
 
 It is also recommended to have a [single assertion per each `waitFor`](https://kentcdodds.com/blog/common-mistakes-with-react-testing-library#having-multiple-assertions-in-a-single-waitfor-callback) for more consistency and faster failing tests. If you want to make several assertions, then they should be in seperate `waitFor` calls. In many cases you won't actually need to wrap the second assertion in `waitFor` since the first one will do the waiting required for asynchronous change to happen.
 
-### Using a React Native version < 0.71 with Jest fake timers
-
-:::caution
-When using a version of React Native < 0.71 and modern fake timers (the default for `Jest` >= 27), `waitFor` won't work (it will always timeout even if `expectation()` doesn't throw) unless you use the custom [@testing-library/react-native preset](https://github.com/callstack/react-native-testing-library#custom-jest-preset).
-:::
-
 `waitFor` checks whether Jest fake timers are enabled and adapts its behavior in such case. The following snippet is a simplified version of how it behaves when fake timers are enabled:
 
 ```tsx
@@ -96,10 +90,6 @@ await waitFor(() => {
 }, 10000);
 ```
 
-:::info
-In order to properly use `waitFor` you need at least React >=16.9.0 (featuring async `act`) or React Native >=0.61 (which comes with React >=16.9.0).
-:::
-
 :::note
 If you receive warnings related to `act()` function consult our [Undestanding Act](docs/advanced/understanding-act.md) function document.
 :::
@@ -129,10 +119,6 @@ This method expects that the element is initially present in the render tree and
 
 You can use any of `getBy`, `getAllBy`, `queryBy` and `queryAllBy` queries for `expectation` parameter.
 
-:::info
-In order to properly use `waitForElementToBeRemoved` you need at least React >=16.9.0 (featuring async `act`) or React Native >=0.61 (which comes with React >=16.9.0).
-:::
-
 :::note
 If you receive warnings related to `act()` function consult our [Undestanding Act](docs/advanced/understanding-act.md) function document.
 :::