[pickers] Add explicit interfaces for components slots and components slots props

[flaviendelangle]

Part of #4466

Goal

Clean the typing of the components and componentsProps props before expanding the usage of the pattern in future PRs.

• The XXXSlotsComponent and XXXSlotsComponentsProps are not nullable, it is the XXXProps interface which has a Partial (like on the DataGrid)

• If the components or componentsProps is defined in one of the interface extended by the current component AND this interface is not tightly linked to the new component, then redefine explicitly components and componentsProps (ie: do not redefine on DesktopDatePickerProps if defined on BaseDatePickerProps, but redefine on CalendarPickerProps if defined on PickersCalendarHeader)

What's next ?

• Add JSDoc to the existing components and there componentsProps
• Add a componentsProps for each existing components like on the DataGrid
• Move the props.XXXXProps and props.XXXXComponent (PopperProps, TransitionComponent, ...) to the slot pattern
• Improve doc generation for the slots of the pickers

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	284.3	504.3	407.9	389.6	75.975
Sort 100k rows	ms	557.5	1,250	789.6	888.72	227.524
Select 100k rows	ms	194.7	405.2	297.2	302.14	85.297
Deselect 100k rows	ms	157.7	215.4	171.8	181.94	21.262

Generated by 🚫 dangerJS against 38f8e3f

[flaviendelangle]

This interface was a copy paste of the one in DateRangePicker/shared