[DataGrid] Refactor: create base Select

[romgrk]

Part of the design-system agnostic work.

Create base Select.

[mui-bot]

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

Generated by 🚫 dangerJS against b15bbe7

[MBilalShafi]

What if we need to pass different props to FormControl/InputLabel for two different BaseSelect usages?

To allow the customizability (e.g. tweaking props passed to FormControl) without changing the function BaseSelect implementation, would it be better to keep components like FormControl and InputLabel separate like before, but make the top level components design-specific provided to the Data Grid using configuration?

For example:

1. GridColumnMenuAggregationItem gets moved to the /material/components
2. It uses FormControl, InputLabel, and Select like today
3. It is passed in configuration from material entry point. (technically it could also be a slot but I think they should be limited to the reusable parts rather than specific components.)
4. Base UI Grid (or another design system) passes a totally different GridColumnMenuAggregationItem component.

In general, if we go this direction, /{design-system}/components could contain more such components which are not generic enough to be slots but their implementation is more binded to a specific design system, they could be passed as configuration.components or similar.

[romgrk]

What if we need to pass different props to FormControl/InputLabel for two different BaseSelect usages?

We can always re-use the slotProps mechanism. I'm trying to limit the exposed API because the amount of work to add another design-system depends on the amount of API to re-implement. I'm open to moving bigger components to design-system folders if necessary.