Automatically get dependencies in the workflow to publish package on PyPI #152
Description
Right now the dependencies of the bindings are manually specified in the pythonpublish workflow. This is problematic when a release contains the addition of a new dependency, as then there is no way to check if the dependencies in the publishing workflow are correct. One way to check this is to do a pre-release using a release candidate, but this is a cumbersome solution. A solution would be to have the workflow detect the dependencies automatically from the pyproject.toml file.
This issue is inspired by the release v2.5.0.0 in which the added dependency of pkgconfig led to the PyPI publication workflow to fail.