Workflow for release

[vineetbansal]

I've created a trusted publisher on my pypi account (any other user can create it too in the future), and added a release workflow on merge to main. The package on pypi will be called pathpyG.

I've bumped the version to v1.0.0.rc1 so a regular pip install pathpyG won't pick it up (yet) - it can be forced it pip install --pre pathpyG. Once we move to regular version numbers, it will work.

This setup has worked for me in other projects, but we'll find out more once we do a test pre-release.

[M-Lampert]

Looks mostly good to me. Only a few minor things:

• The uv.lock-file still contains the old version since it's installed editable: https://github.com/pathpy/pathpyG/blob/02c0dc6a167697d5a4a1296b8a172023d4b78297/uv.lock#L3941
• This triggers for every push to main. Is the idea to prepare new versions always on dev and then push all changes to main at once? Are there any branch protection rules for that? If yes, then we should probably ask @IngoScholtes to enable them once we merge this. I don't think I have enough permissions for that.
• I opened an issue (Proper documentation versioning #337) for what we need to change to make the docs ready for a stable version. I am not sure when it would be best to do this. It might be better in a different PR, just wanted you to be aware of this.