[fields] Play with the Base UI DX

[flaviendelangle]

Not planning to merge this one before a long long time.
The will likely be released after v8 stable (we need Base UI to be stable).

Exploration of #14496 (comment)

Goals of the POC

• Get more familiar with the Base UI DX to better understand the DX choices and ongoing discussions.
• See how the Base UI DX could help us improve visual customization at the field level (e.g: allow people to build fields that keep our editing mechanism but using their design system, which can be in-house or a third party library).
• See how the removal of enableAccessibleFieldDOMStructure will help us simplify the typing and the logic of the fields.

TypeScript

I'm exploring some improvements in this PR, they would be extracted to a standalone PR if we decide to apply them.

• Move some basic pro interfaces in the community package (DateRange, RangePosition and RangeFieldSection to allow interfaces to infer TValue and TSection from TDate. A lot of our interfaces have tons of generics, which is a pain, it would simplify a lot of things if we could infer those:

  -interface MyInterface<TValue, TDate extends PickersValidDate, TSection, TError> { ... }
  
  // At a component level, `TIsRange` is always defined, only `TDate` depends of the app it's being used in
  +interface MyInterface<TDate extends PickersValidDate, TIsRange extends boolean, TError> { ... }

  Not entirely sure how much it improves the logic. It feels good to remove the need for people to import FieldSection, RangeFieldSection and DateRange and instead rely on a TIsRange extends boolean that they will easily understand how to use. I'll keep playing with this change, this is clearly something we could extract and apply v8 if we decide to.

Questions

Package structures

• From where should the Base UI-DX component be exported?
  • @mui/x-date-pickers/base/PickersField => require to handle depth 2 imports
  • @mui/x-date-pickers/PickersField => no way to know which components are using material and which one are not (unless we add a @mui/x-date-pickers/material endpoint and everything outside of it is unstyled).
  • @base-ui/x-date-pickers/PickersField
  • something else?

[mui-bot]

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

Updated pages:

• docs/data/date-pickers/custom-field/custom-field.md

Generated by 🚫 dangerJS against eaee053

[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.

[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.