[pickers] Use context to pass props from the picker to the field

[flaviendelangle]

Part of #16059

This PR only cover the props that are common to all the fields, otherwise it would be too big and hard to review.
For now the validation props and some other prop are still passed to the field using props (see "Follow up" for more details).

• Create a new private context for the properties that are specific to our editing mechanism (let me know if you think those should also be in the public context.
• Use disabled, value and setValue from the existing public context in the field components
• Add fieldFormat and timezone to the existing public context and use them in the field components
• Remove formatDensity and shouldRespectLeadingZeros from useParsedFormat, and make format optional (use the one passed by the picker by default).
• Migrate all the doc demos to use the context instead of internal props for the migrated properties.
• Write migration guide

Follow up

• Use context for readOnly and autoFocus (requires [pickers] Let the field components handle their opening UI, and allow field editing on mobile pickers #15671)
• Use context for validation props (currently handed by each picker individually)
• Use context for inputRef, unstableFieldRef, name and label (need to make single input range fields the default before)
• Use context for ref (currently handed by each picker individually)
• Do the same with the views (probably not during the alpha / beta)

[mui-bot]

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

Updated pages:

• docs/data/migration/migration-pickers-v7/migration-pickers-v7.md

Generated by 🚫 dangerJS against 1eb5669

[github-actions]

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

[flaviendelangle]

• shouldRespectLeadingZeros: I removed it because it was doing nothing since it's a placeholder and a placeholder never has leading zeros 🤦 .

• formatDensity: I removed it, but for this one it's more subjective and I would like your opinion. I can take it from the context and allow an override like for the format. My reasoning behind the removal is that the density is a concept internal to the our field. If someone uses it in a custom field (let say a masked field), then he/she will have an inconsistency between the placeholder (which will have the spaces) and the value (which wont). So I think it's better to just let the user use a good old format.replace(/\//g, ' / ').

• format: I made it optional, by default it's using the one of the picker (or a default date format when using a standalone field but it's probably not a realistic use case)

[michelengelen]

On the formatDensity I do agree ... its probably best to give the user the freedom to use whatever density he prefers and apply it to both. 👍🏼

[flaviendelangle]

We would now be able to make value and timezone optional and read it from the context by default. Same with the validation props in the future.

But I would like to take the time to think this API correctly before doing anything.

[michelengelen]

On the formatDensity I do agree ... its probably best to give the user the freedom to use whatever density he prefers and apply it to both. 👍🏼

[github-actions]

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