[core] Upgrade Toolpad to React 19

[bharatkashyap]

• Fixes Update @toolpad/core to React 19 #4499
• Update react, react-dom, @types/react and @types/react-dom to ^19
• Update all packages across monorepo (including docs and studio*)
• Run npx codemod@latest types-react-codemod preset-19
• Run npx codemod@latest react/19/migration-recipe (excluding react/prop-types-typescript )

[bharatkashyap]

Upgrading all packages allowed most of the breaking types checks to pass, but there are some strange integration test failures.

1. "can move elements in page"

Fails locally as well, moving text fields causes the value to disappear - not sure what's causing this.

@apedroferreira any ideas?

Before	After
normal-swap.mov	r-19-swap.mov

2. "data providers" and "data providers crud"

pass locally, fail in CI

[apedroferreira]

Upgrading all packages allowed most of the breaking types checks to pass, but there is a strange integration test failure, because of a bug I can't really pinpoint the cause of.

Moving text fields causes the value to disappear - not sure what's causing this.

@apedroferreira any ideas?

Before After
normal-swap.mov
r-19-swap.mov

Not sure at first glance... probably something to do with the logic we have for the controlled state and possibly bindings, probably will take some deeper looking into. I could also try once I have the time as I have also touched that logic some time ago.

[apedroferreira]

I found the fix for the text fields, looks like I can't push it to your repo directly?
In the studio components, in Form line 61, change the effect to:

// Reset form in effect as suggested in https://react-hook-form.com/api/useform/reset/
  React.useEffect(() => {
    if (isSubmitSuccessful) {
      form.reset();
    }
  }, [form, isSubmitSuccessful]);

It looks like this effect recommended by react-hook-form runs more times than intended on React 19 and resets the fields.
I think this fix should be fine?

[bharatkashyap]

@apedroferreira @Janpot The two data grid related tests which are exceeding timeouts is most likely due to mui/mui-x#15770 I've skipped those two pending the fix of this issue to unblock the upgrade, wdyt?

The tests pass if I increase the timeout locally to a very high number:

I can not reproduce the Argos change reported as well:
Given that I've approved the change to get this PR to a reviewable stage.