[pickers] Drop allowSameDateSelection prop

[flaviendelangle]

Fixes #4456
Fixes #4727
Part of #4728

Now that we don't fire onChange when the new value is equal to the old one, I don't see any reason to keep this prop.

• On DateTimePicker it is set to true (equivalent to not having it)
• On DatePicker it is set to false and it causes the bug of [DatePicker] Date Picker value cannot be set when changing only the year #4456
• On DateRangePicker it is not used
• On TimePicker it is not used

Behavior

If we click on the current date, it validate just like another date
It will never call onClose since the value did not change since the last value update
It will only call onAccept if another view value has changed

What's next ?

I will prepare a follow up PR to implement mui/material-ui-pickers#1759 (comment)

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	239	506.9	349.1	369.02	116.759
Sort 100k rows	ms	437.5	967.1	759.8	742.16	188.525
Select 100k rows	ms	131.2	199.6	199.4	179.08	27.285
Deselect 100k rows	ms	110	133.8	128.9	125.7	8.197

Generated by 🚫 dangerJS against 168d4d9