Cleanup pyproject.toml

[M-Lampert]

• Remove references to Microsoft
• use uv for dependency management
• Add linting rules
• Add formating rules

[M-Lampert]

I am not sure if it is a good idea to use poetry for dependency management. The last time I checked it had some issues with installing PyTorch and related packages from other sources as you often have to do for GPU support:
python-poetry/poetry#6409
PyG doesn't use it either.
Please let me know what you think.

[hackl]

I never used poetry in combination with PyTorch and PyG. Maybe due to this complexity, we should not implement poetry yet.

[M-Lampert]

We never really implemented a good practice for version management, resulting in bugs like #268 not being caught automatically.
I've recently started using uv for dependency management in my projects, which works similarly to poetry but is much more performant. It also integrates installing specific PyTorch- and PyG-wheels well. So we could think about using that for better dependency and version management.
@hackl what do you think?

[hackl]

I think it would be a good idea to use a dependency management system for pathpyG. It makes things much easier. I never tried uv but we can give it a try. Here a short blog entry about poetry vs uv.

[M-Lampert]

I've also seen that post but the conclusion seems to be out of data according to the update mentioned after the blog:

Update Nov 11, 2024: uv has released multiple updates solving my biggest gripes, and I am now in the process of switching my projects over from Poetry to uv.

Ok, then I will do the migration. Should be easy enough, I've done it a few times in my other projects already. This should also simplify and speed up the building of Docker images and the GitHub pipelines #275. PyG also uses it inside their GitHub workflows.