Whatever Python version we ask for by using the Setup Python GitHub Action is overwritten when we run poetry install by whichever version of Python is defined in the pyproject.toml file. Hence, it does not make sense to either i) define a Python version in the workflow before running poetry install, or ii) running tests across a matrix of Python versions.
This PR is motivated by the following logic: