[core] Fix default props behavior on all pickers

[flaviendelangle]

Change showToolbar default value on DateTimePicker

Fixes #4455

It is simply a migration of mui/material-ui#30258
The default value was yet but the doc was saying otherwise

Apply same code structure for the DateRangePicker as on the other components

All others responsive picker components (TimePicker / DatePicker and DateTimePicker) are just tiny wrappers that calls there mobile and desktop components.

But for the range picker, we had duplication of a large interface + duplication of most code between DateRangePicker, MobileDateRangePicker and DesktopDateRangePicker.

Fix the props priority (component props > theme props > default props)

Fixes #4454

We currently do something like:

const useSomePickerDefaultizedProps = (
  { someProp = defaultValue, ...other },
  name
) => {
  return useThemeProps({ 
    props: { someProp, ...other },
    name
  })
}

So someProp is never undefined when passed to useThemeProps.

I changed it to:

const useSomePickerDefaultizedProps = (props, name) => {
  const themeProps = useThemeProps({ props, name })

  return { someProp: defaultValue, ...themeProps }
}

Others

I also replaced the ternaries by if in the other components.
I don't like the usage of ternaries for long expressions.

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	247.2	518.8	319.2	364.96	111.259
Sort 100k rows	ms	494.5	1,036.2	494.5	811.28	201.205
Select 100k rows	ms	92.4	142.8	141.2	125.56	19.743
Deselect 100k rows	ms	127.1	312.5	191.3	216.74	69.666

Generated by 🚫 dangerJS against 2556721