feat: Dates can now be parsed only as strings, also migrated to the non dep…

[visch]

Closes #1 , #246

[visch]

@edgarrmondragon I think this is interesting. We could offer a way to override the type to be an empty object like "{}" and then force the datatype from psycopg to be a string which with target-postgres also accepting that gives us full end to end string conversion which bypasses type issues if someone hits them

[visch]

@edgarrmondragon I think this is interesting. We could offer a way to override the type to be an empty object like "{}" and then force the datatype from psycopg to be a string which with target-postgres also accepting that gives us full end to end string conversion which bypasses type issues if someone hits them

Thought about this a bit more, and "just" casting everything to a string might be better but that's not super clear to me.

The main benefit of this is you'd get this workflow for users

1. Try to use tap-postgres
2. Hit a type issue (Hopefully they'd submit an issue to the tap)
3. Try the "all strings" config option
4. Hopefully everything just works