[pickers] Stop using utils in locales

[flaviendelangle]

Fixes #13768

I need to avoid 2 type of breaking changes

1. For the people overriding the locale (they must still receive value and utils)
2. For the people overriding a component that calls this translation (the built-in locale must still work even if they don't pass formattedDate yet)

So I'm handling both the old and the new format in each locale.
This is not clean code, but we can clean it easily during the alpha and the end result will be even better than before this PR.

New DX

In v7

const translations = useTranslations();
// TS will complain since we are not passing the utils, but it will work with any built-in locale
const label = translations.openTimePickerDialogue(value, {} as any, value == null ? null : value.format('MM/DD/YYY'));

In v8

const translations = useTranslations();
// TS will complain since we are not passing the utils, but it will work with any built-in locale
const label = translations.openTimePickerDialogue(value == null ? null : value.format('MM/DD/YYY'));

Follow up

• In v8 alpha: Remove value and utils params from openDatePickerDialogue, openTimePickerDialogue and clockLabelText

[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-14505--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 87b392e

[LukasTy]

Thank you for taking care of it! 🙏
The DX looks great. 👍
We are going to clean this up nicely on 8. 👌

[LukasTy]

👏 🚀 💯