Handle empty string values for `datetime`, `date`, and `time` types

[cynthiaxyin]

In the dbt type parsing logic for old normalization, empty string values for these 3 types are always converted to null for all destination types (L534, L558, L583).

In the 1s1t world, how should we handle this?

• Each destination's try-cast logic decides if "" should be a typing error or null. ✅
• Or, different destinations should handle this consistently (when technically possible). The protocol should define whether "" is valid, and enforce that on sources (fail CAT if they produce "") and destinations (fail DAT if they choke on "").

[evantahler]

Grooming:

• we think this already works with our try/catch logic!
• this story is to write a test that confirms updated_at: "" becomes "null" in the column and and error is stored within airbyte_meta

[harsha-mangena]

@evantahler, @cynthiaxyin Can I pick this up?

[cynthiaxyin]

@harsha-mangena Sure! Contributions are always welcome :)