[fields] Use onChange instead of onKeyPress for Backspace editing

[flaviendelangle]

Fixes #10399

After some more investigation, the problem is that the Backspace key is always treated as Unidentified on Android, so it was edited using onChange.
I updated the onChange to work with Backspace editing, removed the Backspace editing from onKeyPress and updated all the tests.

[flaviendelangle]

Before, we were not even calling publishValue.
But it's problematic with Backspace because the state was not updated when pressing Backspace on an already empty section, causing the selection to be removed by the browser.
So now we always update the state but we don't publish onChange if not needed

[flaviendelangle]

Small fix when the active section is already empty
If could never happen before

[mui-bot]

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

Generated by 🚫 dangerJS against 797d1ab

[LukasTy]

Great work! 💯
This has the added benefit of now allowing the full date clearing.
Previously clicking Backspace on Android while having the whole field selected would not correctly clear the field 🙈

I noticed that after these changes there is some sort of flickering happening when deleting a section value on Android, it also happens when trying to delete already empty section.
It seems that visually the section value gets removed and then added back in.
Is there any way we could avoid this, because the UX is not the best now. 🙈

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[flaviendelangle]

I noticed that after these changes there is some sort of flickering happening when deleting a section value on Android, it also happens when trying to delete already empty section.

I I understand the flickering you are talking about, thenI also have the flickering on master
And I did not find a way to fix it when I first did the Android support last year:

mui-x/packages/x-date-pickers/src/internals/hooks/useField/useField.ts

Lines 457 to 460 in 8b67c90

	// If `state.tempValueStrAndroid` is still defined when running `useEffect`,
	// Then `onChange` has only been called once, which means the user pressed `Backspace` to reset the section.
	// This causes a small flickering on Android,
	// But we can't use `useEnhancedEffect` which is always called before the second `onChange` call and then would cause false positives.

I do agree that it's not optimal
In v6 since the section will be alone in its input, the sections further right won't move 👌

[LukasTy]

Sorry for missing the mentioned comment. 🙈
Yeah, it's definitely not a big problem, it's not that you constantly need to delete already empty sections. 😆

[flaviendelangle]

The mentionned comment is in the middle of thousands of lines of code, not easy to spot 👌