[DateTimeRangePicker] Fix OK button behavior

[joserodolfofreitas]

Steps to reproduce

Link to live example: (required)

Steps:

1. go to basic example
2. input the first calendar date and click ok

https://github.com/mui/mui-x/assets/550141/832b74f1-160f-4eec-8997-c7d99d5ad311

Current behavior

If users click the OK button on the start input, it closes the view.

Expected behavior

If users click the OK button on the start input, it should move to the end input.

Context

No response

Your environment

npx @mui/envinfo

  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: datetimerangepicker okbutton

[gitstart]

@joserodolfofreitas we would like to pick this up

[joserodolfofreitas]

Thank you for offering to take on this issue! We really appreciate your willingness to contribute. However, this particular issue can be quite deceiving, in the sense that it looks simple, but it's fairly complex and require deep understanding of the component.

We recommend getting started on issues labeled with "good first issue". https://github.com/mui/mui-x/issues?q=is%3Aissue+label%3A%22good+first+issue%22

Currently, there are no Date pickers issues with that label, but we're looking into that.

[LukasTy]

We decided to go with the suggested approach. The first course of action would be to introduce a new action that would be shown, while the value is "incomplete" (all the specific cases TBD when working on it). We discussed that it would make sense for this action to have a different label (maybe "next"?).