feat: Use SSL and SSH config in LOG_BASED replication

[danilofuchs]

Fixes #469

Problem

There are two libraries used for connecting to the PostgreSQL database, depending on the replication mode:

1. FULL_TABLE and INCREMENTAL: SQLAlchemy + psycopg2
2. LOG_BASED: psycopg2 directly

The SQLAlchemy URL takes into account SSL and SSH configuration options, but the psycopg2 connection uses the raw config values.

Another inconsistency is that application_name=tap-postgres is only set if using the psycopg2 connection.

Solution

Creating a shared ConnectionParameters dataclass which can be built via either discrete config parameters, or via a sqlalchemy_url config. This dataclass can then be rendered as either a SQLAlchemy or a psycopg2 URL

The PostgresLogBasedStream uses the exact same ConnectionParameters as the other streams, via their shared PostgresConnector

Note: I opted to now allow configuring log_based replication with the sqlalchemy_url config, for more flexibility

Questions

1. I was not able to run the SSH tests locally, and am not sure if another container would be necessary for integration tests.

Future improvements

1. Add a new tap option called postgres_options, to allow adding arbitrary PostgreSQL options without bailing out to sqlalchemy_url
2. Allow setting application_name via tap options, perhaps via the above suggested option

[edgarrmondragon]

Thanks @danilofuchs! Just one small nit.

[edgarrmondragon]

Thanks @danilofuchs!

[edgarrmondragon]

• fix: Ensure connection parameters are update to the SSH tunnel host and port #721