Changed datepicker for flatpicker

[rjlanari]

*Replace the old datepicker with flatpickr and connect the flatpickr instances (if there are multiple ones, e.g. for module phases).

• PR name contains story or task reference
• Documentation (docs and inline)
• Tests (including n+1 and django_assert_num_queries where applicable)
• Changelog

[m4ra]

@rjlanari @goapunk the flatpicker in mB works as dropdown, while the one here is similar to datepicker.
from mB dev:

from this a+ PR:

[rjlanari]

@rjlanari @goapunk the flatpicker in mB works as dropdown, while the one here is similar to datepicker. from mB dev:

from this a+ PR:

Hello @mara, why can it be that when I test it locally I get it as dropdown?

[m4ra]

@rjlanari you are right! I didn't rebuild the npm. Works as expected now, I will go ahead and merge. Thank you

[m4ra]

Nice!

[m4ra]

@rjlanari can you run a rebase with main from your branch?

git fetch
git checkout your-branch
git rebase main

if any conflicts that you cannot resolve, let me know in mattermorst.
once done with rebase force push again.

[hom3mad3]

we could add a fallback date format here const format = django.get_format ? django.get_format('DATE_INPUT_FORMATS')[0].replaceAll('%', '') : 'Y-m-d';

[hom3mad3]

I would suggest splitting into smaller, well-named chunks and then call them inside the function. It will make the code easier to read and maintain and we can keep the main initializer nice and clean.

[goapunk]

not sure if that's something @rjlanari wants to take over as the focus was more on django, what do you think @rjlanari ? Otherwise maybe you can work on that @hom3mad3 if you have an idea in mind? If we change it we should port it over to mb (or if both files are identical we could even consider moving it into a4)