(Fix) DatePicker input should clear when unspecified is checked

[ODORA0]

Requirements

• This PR has a title that briefly describes the work done including the ticket number. Ensure your PR title includes a conventional commit label (such as feat, fix, or chore, among others). See existing PR titles for inspiration.

For changes to apps

• My work conforms to the O3 Styleguide and design documentation.

If applicable

• My work includes tests or is validated by existing tests.
• I have updated the esm-framework mock to reflect any API changes I have made.

Summary

This fix ensures that the date input clears correctly when the "unspecified" option is selected, addressing the issue where state changes were not properly propagated to the DatePickerInput component.

Screenshots

Screen.Recording.2024-07-31.at.15.04.49.mov

Related Issue

Other

[ibacher]

See #1099.

[gracepotma]

@ODORA0 I'm so sorry for your experience here with a sudden closure - it turns out the underlying cause was it seems both you and Ian were working on this without both being aware 🥴 This is the ticket and you can see Ian was assigned: https://openmrs.atlassian.net/browse/O3-3505

The other concern was about adding a React state with a component that was always driving that state and overrides the on-change function, which would mean we couldn't implement a custom on-change function, and couldn't use this control in an uncontrolled manner / outside of this particular use-cases. We were concerned about the other use cases this could break.

My process takeaway here is (A) the importance of Jira tickets (unfortunately; I too have a love/hate relationship with Jira as I think we all do 😅) and (B) we should have done a better job abiding by our Contributing Conventions. Again I'm sorry for this experience Jonathan - we plan to keep doing better together 🙏 ❤️