build: add PyPI publish workflow via python-semantic-release + OIDC

[farhan]

Important

PR implemented with the assistance of Claude Code. Refined and validated before being submitted for code review.

Add PyPI publish workflow to mockprock
Part of openedx/public-engineering#506

Summary

• This repo is now PyPI-publishable: https://pypi.org/project/mockprock/
• Switch pyproject.toml from static version = "2.0.0" to setuptools-scm dynamic versioning via git tags
• Rename existing release.yml → npm-release.yml (preserves full git history of the npm workflow)
• Add new pypi-release.yml following org-standard python-semantic-release v10.6.1 + OIDC trusted publishing pattern

Removed/Updated

Renamed workflows:

From	To	Reason
release.yml	npm-release.yml	Explicit naming to make room for the PyPI-standard pypi-release.yml

Added workflows:

Workflow	Purpose
pypi-release.yml	Runs CI → python-semantic-release → uploads dist artifacts → publishes to PyPI via OIDC

Versioning

setuptools-scm with dynamic = ["version"] — python-semantic-release controls the version string at release time via git tags. fallback_version = "2.0.0" is set since existing tags are npm-style (npmv*) which setuptools-scm cannot parse; a custom git_describe_command skips those tags and only matches Python-style version tags (v* or digit-prefixed). The first python-semantic-release run will create v2.0.0 or higher based on commit history.

Important Notes

• OIDC trusted publisher must be configured on PyPI before merging. Go to https://pypi.org/manage/project/mockprock/settings/publishing/ and add a trusted publisher for openedx/mockprock, workflow pypi-release.yml.
• npm-release.yml is unchanged from master — the existing Node.js npm release workflow is fully preserved; only renamed for clarity. Note: npm publishing via this workflow has not been active for some time (see Should @edx/mockprock continue to be published to npm? #69 for context and a question on whether to continue it).
• Both workflows are fully independent — npm-release.yml and pypi-release.yml each call ci.yml independently on push to master with no coupling between them.

Testing Notes

This PR has not been manually tested against the repo's own features. Testing relied on CI checks and local agent tooling (uv lock --check, python -m build). Repo-owner is encouraged to verify the OIDC trusted publisher is configured on PyPI before merging.

---

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (7293e57) to head (0000799).

Additional details and impacted files

@@          Coverage Diff           @@
##           master     #68   +/-   ##
======================================
  Coverage    0.00%   0.00%           
======================================
  Files           7       7           
  Lines         331     331           
======================================
  Misses        331     331           

Flag	Coverage Δ
unittests	0.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.