The project's Python package dependencies are managed using the "Poetry" tool.
Tasks and a GitHub Actions workflow are added to maintain and check for problems in the Poetry configuration files.
The tasks provide the following operations:
* Check for problems with the data structure of the `pyproject.toml` Python project file
* Update the `poetry.lock` file as may be required following manual modifications to `pyproject.toml`, or update of the
 "Poetry" application
A GitHub Actions workflow is included to automatically run the tasks. The workflow is triggered on any push or pull that
changes relevant project files, in order to avoid the introduction of problems with the project filesystem. It is also
triggered periodically, in order to catch breakage caused by external changes.

...ncies` table
Originally Poetry supported two distinct dependency types, each defined separately in the `pyproject.toml` file:
* main: defined under the `tool.poetry.dependencies` table
* dev: defined under the `tool.poetry.dev-dependencies` table
This concept of dependency types was later made more flexible by allowing the user to define any number of arbitrary
dependency "groups", with "dev" simply being one of those groups. A new table naming scheme was created to support this
flexible dependency groups system.
For the sake of backwards compatibility, Poetry does still support use of the `tool.poetry.dev-dependencies` table.
However, it is deprecated and its use results in a warning.
The project's Poetry configuration is hereby migrated to the modern format.