[core] Create dedicated InputComponents for single select and date filters

[alexfauquette]

Context: #3198 (comment)

I have a doubt about the second commit. If the GridFilterInputValue component is used by developers, removing the support for singleSelect type will be a breaking change

[m4theushw]

If the GridFilterInputValue component is used by developers, removing the support for singleSelect type will be a breaking change

We should keep the logic for the singleSelect inside it to not create a breaking change. However, we can add a deprecation message to redirect users to use the new component, only if they use it with a column with type singleSelect.

As example: https://github.com/mui-org/material-ui/blob/857c7ad547207b647094c97be69385c7d921ddc2/packages/mui-material/src/styles/adaptV4Theme.js#L4

[alexfauquette]

I have put Date inputs in a dedicated component because I was looking to modify their InputProps #3222

[flaviendelangle]

We don't we merge the props with TextFieldProps here instead of below ?

[alexfauquette]

Seems that we can not extend with a union of type, so we cannot do

export interface GridFilterInputSingleSelectProps extends GridFilterInputValueProps, TextFieldProps {
  type?: 'singleSelect';
}

[flaviendelangle]

In that case I think we should use a type

export type GridFilterInputSingleSelectProps = GridFilterInputValueProps & TextFieldProps & { type?: 'singleSelect' }

It's not great, but exporting an incomplete interface seems worse to me

[alexfauquette]

I corrected it for the two new components. I can not do it for theGridFilterInputValue because the type GridFilterInputValueProps is already exported. I add it as a comment in the breaking change issue

[m4theushw]

This is not a problem here, but per convention other should always be last prop to be spread.