enh: validate datetime fields

[luka-nextcloud]

• Resolves: Invalid extreme date time value accepted in PostgreSQL causes "Double time specification" error #8369
• Target version: main

Summary

• Improve validation for date fields in card creation and update operations, ensuring that dates are properly formatted and do not exceed the year 9999.
• Also enhance datetime fields handling on frontend to prevent invalid date selections.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Documentation (manuals or wiki) has been updated or is not required

[github-actions]

🐢 Performance warning.
It looks like the query count of the integration tests increased with this PR.
Database query count is now 204658 was 198420 (+3.14%)
Please check your code again. If you added a new test this can be expected and the base value in tests/integration/base-query-count.txt can be increased.

[blizzz]

Already stored values are not repaired, right? One-time repair job could be considered, or command. But I guess it is an edge case, though would be nice for affected users/admins to get out of it?

[github-actions]

🐢 Performance warning.
It looks like the query count of the integration tests increased with this PR.
Database query count is now 206571 was 198420 (+4.1%)
Please check your code again. If you added a new test this can be expected and the base value in tests/integration/base-query-count.txt can be increased.

[github-actions]

🐢 Performance warning.
It looks like the query count of the integration tests increased with this PR.
Database query count is now 206568 was 198420 (+4.1%)
Please check your code again. If you added a new test this can be expected and the base value in tests/integration/base-query-count.txt can be increased.