Django-pg-copy

What's Changed
* Set the `ROLE` before `DROP OWNED BY` by rgs258 in https://github.com/FlipperPA/django-pg-copy/pull/9
* `--no-drop` added as an option to not `DROP OWNED BY` by FlipperPA in https://github.com/FlipperPA/django-pg-copy/commit/c541a4a1498e0d43342a7d7f592fd1a1e2a33631
* Allow overriding the database port in `DATABASES` by sebastian-philipp in https://github.com/FlipperPA/django-pg-copy/pull/6
* Add default settings for `ruff` formatting in `pyproject.toml` with `.vscode` integration

**Full Changelog**: https://github.com/FlipperPA/django-pg-copy/compare/1.1.0...1.2.0

What's Changed
* Explicitly pass the `port` from Django's `DATABASES` setting.
* Migrate the repository to `pyproject.toml` and modern build tools.

**Full Changelog**: https://github.com/FlipperPA/django-pg-copy/compare/1.0.0...1.1.0

What's Changed
* We backup and restore with `--no-owner` and `--no-privileges` to avoid errors when backing up with one username, and restoring with another.
* Update trove classifiers to indicate a production release.

**Full Changelog**: https://github.com/FlipperPA/django-pg-copy/compare/0.5.0...1.0.0

* Passes any runtime errors from command invocation back to the shell as an exit status.
* Support parallelization with the `--jobs` parameter. This can have a **drastic** impact on performance.
* On a benchmark test, this reduced the backup time from 47 minutes to 6 minutes when running with `--jobs=8`.
* Be aware that this will also open 8 connections to your database, and will impact the performance of the targeted database.

* Adds a new option to omit tables from the backup: `--exclude-table-data`, `-e`
* Allows passing multiple tables: `-e bigtable1 -e bigtable2`
* Remove trove classifiers for Python 3.5.

* Adds a new option to omit tables from the backup: `--ignore-table`, `-i`
* Allows passing multiple tables: `-i bigtable1 -i bigtable2`
* This is the final release which will support Python 3.5.