[core] Upgrade monorepo

[cherniavskii]

To include banner from mui/material-ui#36074

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	533.9	823.7	806.2	714.38	127.273
Sort 100k rows	ms	558.2	1,074.5	807.9	850.2	169.764
Select 100k rows	ms	239	288.8	245.2	257.98	20.618
Deselect 100k rows	ms	161.9	284.2	202.3	222.32	49.979

Generated by 🚫 dangerJS against 4b776e7

[LukasTy]

LGTM! 🎉
Maybe Netlify step just a fluke and you only need to re-run the pipeline? 🤔 🙈

[cherniavskii]

That's odd, I still see the v6-alpha in the deployment preview even though the resolved monorepo version points straight to the merge commit with this change: mui/material-ui@c0c3d55

cc @LukasTy

[LukasTy]

Hm... Interesting issue.
I've experienced the same locally, until I've deleted .next folder and restarted the dev server. 🤔
Maybe it's the same in Netlify? It might cache the built resources somewhere until you forcefully remove them. 🙈
TL.DR.: I think it should be fine when new docs are deployed. 🙈

EDIT: It could possibly be asserted by (re)creating a PR from this branch to trigger a deployment on a different "domain"/path.

[cherniavskii]

I've experienced the same locally, until I've deleted .next folder and restarted the dev server. 🤔

That is what I did locally too, but I didn't expect to see this problem in a preview deployment.