Support pyproject.toml

[loeschzwerg]

This is more of a suggestion/scaffolding, than a pre-cooked pull request.
I just found this repository and thought "Cool, I think I might use that for other projects".
The repository did not work out of the box, and there is not really much of a development quickstart.
So I went ahead and kickstarted my development environment.

This is where this PR comes in.
It doesn't deliver the pyproject.toml, but an evaluation environment for the maintainers.
Many build-tools migrate to pyproject.toml, as it finally solves this hassle with packaging nightmare.
https://packaging.python.org/en/latest/guides/writing-pyproject-toml/

If you would like to try a build-tool that gained significant attention in the last time, I recommend uv: https://astral.sh/uv (pip install uv)
It allows automatic venv-management and build tool execution.

Obviously the pyproject.toml is far from merge (e.g. authors...)

But because the project was actually running smoothly with just basic configuration, I felt the maintainers appreciate such ease of use.

What I did to get to this point was rather simple:

# get up and running
uv init --build-backend=setuptools
uv add requests

# to list all available run endpoints
uv run

# and then try the cli
uv run fritzconnection

# and I even tried some build tooling
uv add --dev nox
uv run nox

[kbr]

Thanks for your ideas. Replacing the old fashioned setup.py by pyproject.toml is indeed on the bucket list for the future. Regarding uv: as astral has been aquired by OpenAI the future of uv may be bright or not. We will see. Beside this I'm more team pixi. In case you want to have a closer look: https://pixi.prefix.dev/