chore(deps): bump pytest-postgresql from 3.1.3 to 5.0.0

[dependabot]

Bumps pytest-postgresql from 3.1.3 to 5.0.0.

Changelog

Sourced from pytest-postgresql's changelog.

5.0.0 (2023-05-20)

Breaking changes

• Drop support for Python 3.7 ([#706](https://github.com/ClearcodeHQ/pytest-postgresql/issues/706) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/706>_)

• psycopg is now a mandatory requirement. With pyscop2 it was optional due to the different ways it could be installed:

  • psycopg2 - that built itself
  • psycopg2-binary - binary distribution
  • psycopg2cffi - pypy enabled version

  Since psycopg version 3 there's only one package to install. ([#744](https://github.com/ClearcodeHQ/pytest-postgresql/issues/744) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/744>_)

• Dropped --postgresql-logsprefix/postgresql_logsprefix options. All fixture data is already distinguished by tmpdir itself. ([#748](https://github.com/ClearcodeHQ/pytest-postgresql/issues/748) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/748>_)

Features

• Re-rise FileNotFound errors with more meaningful messages. ([#598](https://github.com/ClearcodeHQ/pytest-postgresql/issues/598) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/598>_)
• Support Python 3.11 ([#678](https://github.com/ClearcodeHQ/pytest-postgresql/issues/678) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/678>_)

Miscellaneus

• Drop PyPy from CI ([#669](https://github.com/ClearcodeHQ/pytest-postgresql/issues/669) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/669>_)
• pytest-postgresql will now recognise and use development postgresql versions ([#691](https://github.com/ClearcodeHQ/pytest-postgresql/issues/691) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/691>_)
• Use towncrier to maintain project's newsfragments/changelog ([#700](https://github.com/ClearcodeHQ/pytest-postgresql/issues/700) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/700>_)
• Move project dependency management to pipenv ([#701](https://github.com/ClearcodeHQ/pytest-postgresql/issues/701) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/701>_)
• Migrate to shared automerge workflow for automatic tests dependency updates ([#702](https://github.com/ClearcodeHQ/pytest-postgresql/issues/702) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/702>_)
• Use tbump instead of bumpversion to manage versioning and releases. ([#703](https://github.com/ClearcodeHQ/pytest-postgresql/issues/703) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/703>_)
• Move most of package configuration to pyproject.toml ([#704](https://github.com/ClearcodeHQ/pytest-postgresql/issues/704) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/704>_)
• Introduce Typed config dict ([#706](https://github.com/ClearcodeHQ/pytest-postgresql/issues/706) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/706>_)
• Use ankane/setup-postgres@v1 to setup postgresql in CI instead of custom scripts. ([#708](https://github.com/ClearcodeHQ/pytest-postgresql/issues/708) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/708>_)
• Pass codecov_token to codecov action to upload coverage. ([#721](https://github.com/ClearcodeHQ/pytest-postgresql/issues/721) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/721>_)
• Replaced flake8 and pydocstyle with ruff, turned on isort rules ([#735](https://github.com/ClearcodeHQ/pytest-postgresql/issues/735) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/735>_)
• Split single bid test job into smaller running each after another. ([#740](https://github.com/ClearcodeHQ/pytest-postgresql/issues/740) <https://https://github.com/ClearcodeHQ/pytest-postgresql/issues/740>_)

4.1.1

Misc

• Error message typo fix
• Docker documentation example typo fixes

... (truncated)

Commits

• a532785 Release 5.0.0
• 99cea01 Revert "Publish package with trusted publishers"
• 87af7c3 Merge pull request #751 from ClearcodeHQ/new-publish
• 95de132 Publish package with trusted publishers
• 066959a Merge pull request #750 from ClearcodeHQ/file-not-found
• 1d17def Better exception messages when we could not find proper executable - closes #598
• 9d314a2 Merge pull request #749 from ClearcodeHQ/drop-logfile
• 1d30d47 Dropped --postgresql-logsprefix - closes #748
• 5238708 Bump ruff from 0.0.267 to 0.0.269
• 7112408 Bump ruff from 0.0.267 to 0.0.269
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[di]

Blocked on #10742.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.