Move setup.py metadata and as many tool configurations into `pyproject.toml` as possible

[mhucka]

Is your feature request related to a use case or problem?

Following modern best practices, the project metadata that is currently in setup.py should be moved into pyproject.toml. In addition, many tool configurations can be moved out of individual rc files and into pyproject.toml too. I did this for qsim and it has worked out well.

What solution or approach do you envision?

Start by looking at the various dot files in the repo and seeing how the settings can be written equivalently in the pyproject.toml file.

How urgent is this for you?

None

[rosspeili]

Hey @mhucka happy to take this on.

[mhucka]

@rosspeili Thank you for offering!

I would model this on qsim's pyproject.toml. That one was recently modernized and organizes dependencies in a way that follows modern practices, such as using dependency groups.

It would be great to make this work with uv too.

[rosspeili]

@mhucka I opened a PR, moved packaging metadata into pyproject.toml (qsim-style, with a dev dependency group for uv). Could you take a look when you have a moment and let me know if this matches what you had in mind, or if you'd prefer a different split for follow-up PRs (eg. pylint config migration)?