[pickers] Use usePickerContext() and usePickerActionsContext() instead of passing props to the shortcuts and toolbar slots

[flaviendelangle]

Closes #15495 ( 🙏 )

What?

• Remove the last props passed to the shortcuts, layout and toolbar slots
• Introduce a new useIsValidValue hook to avoid passing something to usePickerContext that updates on every render
• Add value to usePickerContext
• Add setValue to usePickerContext and usePickerActionContext. This should eventually be the only way for parts of the UI to update the value (it will replace the onChange prop passed to the views and to the field in the future).
• Rename PickerShortcutChangeImportance into PickerChangeImportance since it's not only used for the shortcut anymore.

Changelog

Breaking changes

• The component passed to the layout slot no longer receives the value, onChange and onSelectShortcut props — Learn more.

• The component passed to the toolbar slot no longer receives the value, onChange and isLandscape props — Learn more.

• The component passed to the shortcuts slot no longer receives the onChange, isValid and isLandscape props — Learn more.

• The PickerShortcutChangeImportance type has been renamed PickerChangeImportance — Learn more.

[mui-bot]

Localization writing tips ✍️

Seems you are updating localization 🌍 files.

Thank you for contributing to the localization! 🎉 To make your PR perfect, here is a list of elements to check: ✔️

• Verify if the PR title respects the release format. Here are two examples (depending if you update or add a locale file)

  [l10n] Improve Swedish (sv-SE) locale
  [l10n] Add Danish (da-DK) locale

• Update the documentation of supported locales by running pnpm l10n
• Clean files with pnpm prettier.

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

Updated pages:

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

Generated by 🚫 dangerJS against 361fb4a

[flaviendelangle]

For now it's a super dumb hook.
It re-renders everytime the picker render and just calls the function that the picker gives him (which calls the validation).

But introducing this hook will allow us in the future to add it to the Date Calendar and Digital Clock as well and potentially to add some caching mechanism to avoid testing several times the same date.

For now it's only needed for the shortcut slot because we were passing this isValid prop.
When the view and the field will use it, it will probably impact the shape of the context(s) related to validation, but I'm pretty sure we will still have a hook with this exact signature 👌

[flaviendelangle]

In the Base UI version we won't have a notion of shortcut, so this field will probably only live in the MUI version (since some people needed it).

The other will be handled by the Base UI layer.

[michelengelen]

Looks good i general ... only concern is that we could simplify all places where we check for value == null || !utils.isValid(value) into utils.isValid(value) ... agree?

[michelengelen]

Only nits... feel free to ignore... I love the cleanup! Much more readable now! Thanks for taking care of it! 🙇