🐛 DateRangeInput date glitch

[LaurentDario]

This is a very specific bug that seems to be coming up with a few manipulations.
The date of the field on blur is not reflecting the value that is visible on focus.

Describe the bug

If you play around with dates and change them for dates that shouldn't be valid (start date > end date), you can sometimes see one of those dates changing on focus (after insisting).

Steps to reproduce

Go on the Default example of the Orbit doc for DateRangeInput, enter 2 dates that are matching the logic of startDate < endDate. Change the end date for a date prior to the start date, move the focus out of the field. Do it a second time.
You can then see the date changing on the next focus/blur.

Expected results

The date stays consistent with the startDate < endDate logic

Reproducible demo

https://share.getcloudapp.com/qGuRoJAL

[patricklafrance]

It is indeed a bug and it's been reported by Laurent more than a year ago.

Could it be prioritized @fraincs @alexasselin008 ?