This issue was found in a scenario where I needed to update the selectedDate without clicking into
the component, just by passing a value to the Datepicker, and actually it just accepts changes by
clicking which I don't believe covers the use cases.

Cleaning code

Tests stopped running locally, running it on the pipe

Comments removal

…agement according view/date

chore: removing screen.debug

…y selected date by using null"

Attributed null as a acceptable value to the selectedDate, also removed default args for weekstart
which was crashing the app due to an overlap with the component props

1039

Clear should affect dateValue

…se scenario texting property

Updated datepicker component storybook file controls, added the new property and its type so the dev
can simulate scenarios on storybook

Changed the name from labelempty to label

Now datevalue expects null to clear date, also a diff mechanism was added on the dateValue useffect
to prevent mass re-renders.

g

Now datepicker component accepts value and defaultValue as props comes from this is the most
intuitive pattern.

BREAKING CHANGE: A breaking change which affects the old property defaultDate being named now
defaultValue.

Setting defaultvalue to empty when the component loads, therefore updating its sideffects on
mounting considering dateview initialization | Added test cases to these scenarios | Added propper
naming and default values according flowbite patterns

BREAKING CHANGE: New defaultValue initialization value | Migrating from defaultDate to defaultValue