[core] Add React 18 to peer dependencies

[m4theushw]

CodeSandbox: https://codesandbox.io/s/datagridprodemo-material-demo-forked-qvr2t0?file=/demo.tsx

In the comments, I explain the changes I had to make. I updated the peer deps of the date picker components but I don't know if they are compatible, are they? We didn't really test it in React 18 so one way to review this PR could be to open the example above and check if all features still work as expected. The tests are passing in React 18. #4155

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	348.1	409.7	350.5	367.14	24.234
Sort 100k rows	ms	461.4	893.8	721.9	690.88	140.71
Select 100k rows	ms	104.2	186.3	124	136.96	28.779
Deselect 100k rows	ms	99.3	288.1	193.5	178.22	62.821

Generated by 🚫 dangerJS against 462bd07

[m4theushw]

Fixes the following glitch:

From what I found, React 18 doesn't commit some renders if they take too much time. But, no matter the case, we update the render zone position so the position ends not matching the context rendered. Flushing the tree ensures that no render will be skipped. facebook/react#18402 (comment)

Updating the position inside React.useLayoutEffect also didn't work quite well. Here's the result:

I would like to see how other virtualization libraries will solve this problem. Until there we have to use this workaround. If you have suggestions to improve this please comment.

[m4theushw]

Fixes

[flaviendelangle]

Could not find any issues, I guess we will have better feedbacks once the community start using it

[cherniavskii]

Should we start using React 18 in our docs? This may help to discover issues sooner. What do you think?

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[m4theushw]

Should we start using React 18 in our docs? This may help to discover issues sooner. What do you think?

@cherniavskii I'm waiting for the core to update first. Keeping two versions of React may not work correctly. Once the core updates we can merge #4155.

[jeveloper]

Thank you and i'm glad to see these amazing changes.
However, wouldn't the main lib mui/material be in conflict as it stricty supports only up to react 17?
I don't assume the main lib is getting overhauled this quickly to match depdencies.

Thanks

[m4theushw]

However, wouldn't the main lib mui/material be in conflict as it stricty supports only up to react 17?

@jeveloper No, the latest version of @mui/material is already updated to support React 18.