[fields] Correctly handle events with a complete value insertion

[LukasTy]

This fix resolves the issue mentioned here: #9165 (comment)

Calling fill('04/11/2022') (in playwright and possibly other e2e frameworks) on the pickers field does nothing because we explicitly check only the event.target.value.
In such case event.target.value will equal 04/11/2022/MM/YYYY, which is not valid as per our code and nothing happens.

With the change done here, we'd use the event.nativeEvent.data, which would contain the whole 04/11/2022 and update the value using it, instead of the regular section updating process.

When using regular editing by typing characters with the keyboard results in event.nativeEvent.data having only the changed character.

[mui-bot]

Netlify deploy preview

Netlify deploy preview: https://deploy-preview-9896--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	321.8	486	392.6	386.48	58.689
Sort 100k rows	ms	666.3	1,428.4	1,379.1	1,178.5	270.962
Select 100k rows	ms	644.9	761.7	696.7	706.46	43.434
Deselect 100k rows	ms	116.2	223.4	147	166.7	39.772

Generated by 🚫 dangerJS against 1efd153

[alexfauquette]

Are we sure it can not be more than one character? I'm thinking about special keyboards or some auto-completion

I don't see issues, it's just to share a point of attention. I first thought about #9465 but it's not the same problem since IME keyboard calls multiple times the onChange

[LukasTy]

Are we sure it can not be more than one character? I'm thinking about special keyboards or some auto-completion

I'm definitely not sure that there wouldn't be any edge cases, but autocompletion is turned off, although, if any extension hacks it's way into this, I'd imagine that this change could only fix it and not break because it would probably use a similar API of emitting a change event with the full value string. 🤔