[fields] Fix usage of slotProps.textField.InputProps

[flaviendelangle]

Part of #8322

[mui-bot]

Netlify deploy preview

Netlify deploy preview: https://deploy-preview-8428--material-ui-x.netlify.app/

Updated pages

No updates.

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	733.9	880.2	816.9	813.72	47.435
Sort 100k rows	ms	661.9	1,268.2	661.9	958.36	210.371
Select 100k rows	ms	269	380.2	320.5	323.96	35.766
Deselect 100k rows	ms	139.8	263.7	218.9	209.1	41.284

Generated by 🚫 dangerJS against 5e839fa

[alexfauquette]

I don't see reason to say it's a bad pattern, but it's the first time I see a mutation in React code

[flaviendelangle]

For me it's OK because we know that the object is generate on useSlotProps above, so the location is locale (it has no impact before line 28 and after line 38.

[alexfauquette]

I'm not sure to get why modifying the single input range and not the multi input

[flaviendelangle]

@alexfauquette because the conflict is between props received by the field at the top level (e.g: props.InputProps) and received by the field in the textField slot (e.g: props.slotProps.textField.InputProps).
But the multi input fields don't have a top level InputProps since they spread their props to a Stack instead of a TextField.

So no need to do any manual merge, it's always the slot InputProps which wins since it's the only InputProps.