build: automatic nb stripping and pypi upload

[janfb]

• add script for stripping notebook output
• add it to docs CI to automatically strip notebooks before building the docs
• add workflow for the automatic upload to PyPI upon a new release.
• add trusted publisher to sbi PyPI project

Relevant links

• https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
• https://docs.pypi.org/trusted-publishers/adding-a-publisher/

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.28%. Comparing base (becc93c) to head (5f5cf9e).
Report is 3 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1267       +/-   ##
===========================================
- Coverage   89.24%   78.28%   -10.96%     
===========================================
  Files         119      119               
  Lines        8691     8698        +7     
===========================================
- Hits         7756     6809      -947     
- Misses        935     1889      +954     

Flag	Coverage Δ
unittests	78.28% <ø> (-10.96%)	⬇️

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

see 33 files with indirect coverage changes

[janfb]

My fist approach was to using the full tutorial template from https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

With this approach, we would make a test release on every push to main using testPyPI. However, this fails because the version number would be the same, which is not allowed by PyPI (see pypa/packaging.python.org#804).

A solution would be using setuptools-scm to automatically determine version numbers also during development, i.e., in between public releases (explained here https://stackoverflow.com/questions/73605607/how-to-use-setuptools-scm). But my feeling is that this would be an overkill for now.

Thus, I suggest that we "just" use a GH Action triggered when we do a manual release via GitHub (bump version manually, update the changelog, paste changelog into release section and create a tag). This action will build the sbi distribution, upload it to PyPI, and create a signed release with SigStore.

[michaeldeistler]

This is awesome! Questions and comments below :)

[michaeldeistler]

LGTM, thanks!

[tomMoral]

Late to the party but it looks super nice :)