[DateRangePicker] Fix keyboard selection

[alexfauquette]

Fix #5231
Fix #5284

I remove the skip on the date range picker keyboard setting. But it does not catch the bug of the key pressed ignored, so I added another one

I ensured that the input value is reset only when the rawValue is modified by looking at how useAutocomplete works

[mui-bot]

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	240.8	464.9	394.3	350.82	86.237
Sort 100k rows	ms	502.7	805.9	711.9	681.5	112.649
Select 100k rows	ms	135.9	208.4	161.5	163.14	25.865
Deselect 100k rows	ms	110.5	285.9	162.2	184.58	61.76

Generated by 🚫 dangerJS against fece62c

[N1mi1]

Looks like a good bug fix.
Probably the bug caused by the remaining debts mentioned here:

Implement with controlled vs uncontrolled rawValue

Could not reproduce the bug in the deployed Netlify link.

Edit:
Now noticed there is a failed check in the Checks tab, and this PR is a draft ATM 😕.

[github-actions]

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

[subvertallchris]

We just started running into this. I see it's happening on the demo page in the docs, too. https://mui.com/x/react-date-pickers/date-range-picker/#basic-usage

Are there any good workarounds that affected folks can use in the meantime?

[alexfauquette]

@subvertallchris Except staying at alpha-5 I do not see a workaround

@flaviendelangle

[JonathanGuo]

We are running into the same issue too. The fix in CSB is working perfectly. Is there any plan to roll out the fix in the next release?

[alexfauquette]

Will be in the next release