Implementation for date & time types

[kgodey]

Problem

Users will want to store date and time data in columns. We should allow them to do so and implement this type appropriately in the backend.

Proposed solution

We should support Date/Time types in Mathesar and allow users to use them.

Tasks that need to completed:

• Design for date & time data types #240
• Handle TIMESTAMP data type in the backend #424
• Handle DATE data type in the backend #425
• Handle TIME data type in the backend #426
• Implement filtering options for date & time types #427
• Implement display options for date & time types #428
• Spec for human readable date and time parsing #845
• Split Date & Time data type into three Mathesar types  #960
• Return RFC 3339 (ish) style date / time values from API #1086
• Implement grouping options for date & time types #429
• Decide on date/time formatting string syntax #1108
• Frontend implementation of Date & Time Mathesar types #260

Additional context

Related issues and discussions:

• Mapping DB data types to Mathesar data types #269
• Controlled casting for dates, times, and timestamps #128
• Timezones #119 discussion

Also see Postgres "Date/Time Types" docs.