Description of the issue

Typing dates with wrong format in "Cluster history" tab makes appearing error messages which read "The start(end) date cannot be in the future.". This happens only for given kind of "invalid date" like "2024-0221t" but not for input like "2024-02-21t".
It would be better always detecting bad format in order to show the right message "Invalid: YYYY-MM-DD".

Steps to Reproduce:

1. Launch OCM UI staging.
2. Open a cluster and go to a cluster history tab.
3. In one of the date field, type wrong date like "20-02q" or "a2024-01C"
4. See the behavior.

Actual results:

The error message shown is "The start date cannot be in the future."

Expected results:

The expected error message would be "Invalid: YYYY-MM-DD"