[pickers] Prepare compatibility with @mui/zero-runtime (stop using ownerState in styled)

[flaviendelangle]

Part of #12277

Follow up

• Make sure that we are always accessing theme.direction from somewhere compatible with @mui/zero-runtime

  Requires [zero-runtime] Add RTL support material-ui#41217

[mui-bot]

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

Generated by 🚫 dangerJS against db6bd2d

[flaviendelangle]

Right now the typing comes from the DOM element which also accepts "true" and "false"
But we are only passing true of undefined so I restricted the typing so that our check in the styled component and the typing are coherent

[LukasTy]

Great work! 👏 🚀
Leaving some comments about a few regressions. 🙈 💡

[LukasTy]

Great work, thank you! 👍 💯

[siriwatknp]

Suggested change

	})<DateTimeRangePickerStartOrEndToolbarProps<any>>({
	})<DateTimeRangePickerStartOrEndToolbarProps<any> & { ownerState: DateTimeRangePickerStartOrEndToolbarProps<any> }>({

This would make sure that the styled-component receives ownerState.

[flaviendelangle]

DateTimeRangePickerStartOrEndToolbarProps already contains it 👍

type DateTimeRangePickerStartOrEndToolbarProps<TDate extends PickerValidDate> =
  DateTimePickerToolbarProps<TDate> & {
    ownerState?: DateTimeRangePickerToolbarProps<TDate>;
  };

[flaviendelangle]

OK the problem was that ownerState was optional in DateTimeRangePickerStartOrEndToolbarProps

[flaviendelangle]

But the right API here is :

      props: ({ toolbarVariant }: DateTimeRangePickerStartOrEndToolbarProps<any>) => toolbarVariant !== 'desktop',

In which case I do need the typing because the types equals props and not props & ownerState (it should probably be fixed)