[EPIC] Support all possible data-types for database destinations

[alexandr-shegeda]

Tell us about the problem you're trying to solve

We want to reach 99% reliability of our database connectors.
The first phase is to fix the existing issues listed here:

• Destination S3 to Parquet/Avro: Handle empty objects with additionalProperties=true #4608
  • Assigned to @tuliren.
• Json / Avro schema converter should support $ref and remote URLs #5030
• Destination acceptance tests: verify that a destination is able to write any ISO8601-compliant date string #5712
• Mysterious switch of data type for <_airbyte_emitted_at> field crashes incremental jobs #5959
• Destination BigQuery Desnormalized: JSON table encountered too many errors, giving up. Rows: 1; errors: 1. Please look into the errors[] collection for more details #6638
• Use SUPER data type on Redshift destination for raw JSON data #5050
• Destination S3: Support writing timestamps #4610
• Bigquery destination SCD table does not work with array type from source Postgres table #4357
• Destination Azure Blob Storage: Support writing timestamps #6063

[matthieuUrsa]

Do you have a idea when those modification gonna be done and deploy?

[grishick]

We still need to add support for:

• millisecond precision
• Era (BC/AD)
• +/-Infinity
• NaN