fix: EXPOSED-36 LocalDate comparison in SQLite

[bog-walk]

LocalDate value was being passed to database as java.sql.Date, stored as a 13-digit integer because the object represents milliseconds since 1970-01-01. Date datatype in SQLite passed to date functions as an integer must be of a specific format, 10 digits, to represent the number of seconds since 1970.

Conversion to a recognizable format could be achieved by changing the dialect's date functions, like year() e.g.:
STRFTIME('%Y', date_column / 1000, 'unixepoch')
But this would break cases where the same date functions are used for LocalDateTime values.

Date value is instead passed to database as a string, since multiple formats are recognized for comparison.

To match this changed format, LocalDate column representation was also switched to TEXT , one of 3 supported storage types.

Initially, DateColumnType was set as DATE for all databases. SQLite does not have a date-specific column and would instead assign the type as NUMERIC, based on type affinity, with numbers representing seconds since 1970-01-01.

[Tapac]

LGTM, except that it's not implemented for jodatime module.
Also, I would suggest to use DATE time instead of NUMERIC in tests (despite the fact that it has the same representation in SQLite) to get "regression" more strict, as you change the type from DATE -> TEXT

[e5l]

lgtm