[scheduler] Remove unnecessary useMemo usages

[mnajdova]

This PR removes unnecessary usages of useMemo over props that are passes in the useRenderElement hook.

Example usage:

 const props = React.useMemo(() => ({ role: 'gridcell' }), []);

 const element = useRenderElement('div', componentProps, {
    ref: [forwardedRef, dropTargetRef, listItemRef],
    props: [props, elementProps],
  });

The useRenderElement hook will more or less conver the call to

<div {...mergeProps(componentProps, props, elementProps)} ref={mergedRefs} />

so there is no need for memoization. On the opposite side, memoizing would just add more overhead. The transformation should also improve readability as a bonus.

[mui-bot]

Deploy preview: https://deploy-preview-20133--material-ui-x.netlify.app/

Bundle size report

Bundle	Parsed size	Gzip size
@mui/x-data-grid	0B(0.00%)	0B(0.00%)
@mui/x-data-grid-pro	0B(0.00%)	0B(0.00%)
@mui/x-data-grid-premium	0B(0.00%)	0B(0.00%)
@mui/x-charts	0B(0.00%)	0B(0.00%)
@mui/x-charts-pro	0B(0.00%)	0B(0.00%)
@mui/x-charts-premium	0B(0.00%)	0B(0.00%)
@mui/x-date-pickers	0B(0.00%)	0B(0.00%)
@mui/x-date-pickers-pro	0B(0.00%)	0B(0.00%)
@mui/x-tree-view	0B(0.00%)	0B(0.00%)
@mui/x-tree-view-pro	0B(0.00%)	0B(0.00%)

Details of bundle changes

Generated by 🚫 dangerJS against f9b5cbb

[flaviendelangle]

I saw components on Base UI (e.g PreviewCardBackdrop) where we just inline the props object inside useRenderElement() instead of creating a props variable before.

No strong preference here 👍

[mnajdova]

I was wondering the same, I wasn't sure if it helps with readability. If the props object grows I would prefer to have it in a separate object to not pollute the useRenderElement call. But in these cases it's probably the same. Up to what you prefer, as you will be reading this code more often :) cc @mui/explore

[mnajdova]

I will leave this for future refactor, for now, let's just remove the unneeded useMemos.