Update PyPI publish workflow for prereleases

[matentzn]

Workflow now triggers on published and prereleased events, sets PEP 440-compliant version for prereleases, and adds 'skip-existing' to PyPI publish step. Improves handling of pre-release publishing and artifact management.

Resolves #490

• docs/ have been added/updated if necessary
• make test has been run locally
• tests have been added/updated (if applicable)
• CHANGELOG.md has been updated.

[Copilot]

Pull Request Overview

This PR updates the PyPI publish workflow to properly handle pre-releases by triggering on both published and prereleased events, implementing PEP 440-compliant versioning for development snapshots, and adding skip-existing functionality for artifact publishing.

• Expands workflow trigger from only published releases to include prereleases
• Implements automatic PEP 440-compliant versioning for prereleases using date, run number, and git SHA
• Adds skip-existing option to prevent PyPI publish failures on duplicate uploads

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/pypi-publish.yaml	Updates workflow triggers, adds prerelease versioning logic, and improves PyPI publish configuration
CHANGELOG.md	Documents the new pre-release functionality for development snapshots

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Pull Request Overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[gouttegd]

Looks good to me.

You might want to add some notes somewhere that it is the responsibility of whoever wants to do a ”pre-release” to remember to create the release tag accordingly (i.e. a release tag that includes a aN, bN, .devN suffix, depending on the desired type of pre-release).