fix: DateSelector selector validation message issues

[YuvalMasada]

@NoamGaash - This time at the right direction
I've added 2 short fixes.

1. For wrong validation message I added a different message for the specific case. The message will pop for min/max, but I think that the max message will never appear( so maybe it would be better to delete it? not 100% sure ).
2. To make the message re-render when language changed I've extend the useMemo dependency array with t function that should be reassign as the DateSelector component been re-rendered.

[github-actions]

Preview: https://s3.amazonaws.com/noam-gaash.co.il/9959679014/open-bus/40/index.html
Preview Storybook: https://s3.amazonaws.com/noam-gaash.co.il/9959679014/open-bus/40/storybook/index.html

[NoamGaash]

Maybe it would be better if we'll just remove the useMemo hook

[YuvalMasada]

@NoamGaash
It's a good idea to remove it.
while removing it I had thought about 2 how to implement it.

1. Just removing the useMemo and use the function.
2. Take the function out of the component( and remove the useTranslation also) - will look better.
   does it matter which approach I go forward with? I did both of them and it works.

[NoamGaash]

That's up to you
I'd like to make a third suggestion -

1. the function could return the translation key
2. the function can be inside the scope of the component, or underneath

[NoamGaash]

I made a suggestion - it will let you keep using useTranslation which is better approach as it will trigger re-render on language change

[YuvalMasada]

@NoamGaash
At first I did something like your suggestion, but then typescript got mad at me.
It doesn't like that getErrorMessage can return undefined( the t function we got from the useTranslation hook).
I'll be happy to understand why typescript complain about it.

[NoamGaash]

@YuvalMasada I'll try