Parse conninfo string in osm2pgsql-replication

[rustprooflabs]

This is an attempt to fix #1643. This updates osm2pgsql-replication to parse a conninfo string passed to the -d option when psycopg3 is used. If pyscopg2 is installed on the system it fails in its current state. I glanced through the psycopg2 docs and do not see a similar functionality to what is available in the new version. If this looks like a decent direction to head for this fix I can work on making this change not fail with psycopg2.

This now works.

osm2pgsql-replication status -d postgresql://myuser:mypassword@myhost/pgosm
Using replication service 'http://download.geofabrik.de/north-america/us/district-of-columbia-updates', which is at sequence 3257 ( 2022-02-24T21:21:27Z )
Replication server's most recent data is 1 day(s) 2 hour(s) 8 minute(s) old
Local database is 29 sequences behind the server, i.e. 4 week(s) 0 day(s) 23 hour(s) 59 minute(s)
Local database's most recent data is 4 week(s) 2 day(s) 2 hour(s) 8 minute(s) old

[lonvia]

Looks like parsing the DSN needs to be done in a completely different way in psycopg2 and psycopg3. So that will only work with lots of fiddeling, I'm afraid.

What works for both is the dsn parameter for connect. So I would rather check if the dbname parameter looks like a connection string (presence of = or ://) and then feed it in as a DSN.

[rustprooflabs]

This now uses the simpler approach of checking for those string parts. This seems to work with psycopg2 and psycopg3 now.

[lonvia]

That looks much simpler. :) Do you prefer to squash the commits before I merge?

[lonvia]

Bother, I thought I had already pressed the merge button. Thanks for looking into this.

[rustprooflabs]

Thank you!