Use a temporary docker postgres container for postgres DB sync tests

[austinweisgrau]

Should follow #1242

Uses the testcontainers package to easily generate and use a temporary postgres docker container for tests. Allows for running tests on postgres without running a persistent server separately, which should enable us to run tests on postgres in the CICD environment.

[bmos]

this is such a great idea!!
we might also be able to use this approach for other database packages...

[bmos]

If you could run ruff format and ruff check --fix and push the changes, it'll re-run the tests. I'd be happy to help get it working.

[austinweisgrau]

The MacOS test runner does not allow for running docker containers - I made a change in 9d64d41 to skip the tests involving a docker container if docker is not available in the environment

    try:
        import docker

        docker.from_env().ping()
    except Exception:
        pytest.skip("Docker not available")

[austinweisgrau]

Turns out you can't run docker in a Windows github actions environment either, so I took a slightly more robust skipping approach in 651cb39

    container = PostgresContainer("postgres:9.5")
    try:
        container.start()
    except Exception as e:
        pytest.skip(f"Could not start Postgres container: {e}")

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
parsons/databases
alchemy.py
table.py
parsons/databases/postgres
postgres.py					104
postgres_core.py
postgres_create_statement.py
Project Total

This report was generated by python-coverage-comment-action

[bmos]

Suggested change

	testcontainers==4.9.0
	testcontainers==4.14.1

might as well use the latest version here

[bmos]

should 5432 be a string like in test_postgres.py?