[pickers] Add referenceDate on picker components (and DateRangeCalendar)

[flaviendelangle]

Fixes #6870
Fixes #5702

[mui-bot]

Netlify deploy preview

Netlify deploy preview: https://deploy-preview-9991--material-ui-x.netlify.app/

Updated pages

• docs/data/date-pickers/base-concepts/base-concepts.md
• docs/data/date-pickers/date-calendar/date-calendar.md

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	-208.6	-65.4	-151.1	-129.36	48.06
Sort 100k rows	ms	614.8	1,355.7	1,201	1,089.7	252.46
Select 100k rows	ms	562.4	702.5	602.1	629.28	54.981
Deselect 100k rows	ms	111.6	191	149.7	149.88	25.223

Generated by 🚫 dangerJS against 200ac53

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[flaviendelangle]

Conclusion in our weekly meeting

We create one new section in Base concepts (named Reference date when there is no value defined or something similar).
In this section, we talk about the default behavior (we use the validation props). And we add an example of how people can override it using referenceDate.

Based on the issues that made us create this prop, we create sections on component pages (DigitalClock and DateCalendar probably) where we show how to solve those product issues (for example on the DateCalendar it would be something like Choose the initial month and year).

[LukasTy]

Great work finalizing the referenceDate feature! 💙

Is my memory deceiving me, but didn't we have issues, where people wanted to have a certain reference date used and allow selecting only day and month?
If that is indeed true, do you think it's worth having a demo about it? 🤔

[flaviendelangle]

Didn't we have issues, where people wanted to have a certain reference date used and allow selecting only day and month?

I don't recall it, but if we can find the issue sure!