Refactoring Docs to use JupyText

[rlundeen2]

Description

This PR refactors the docs to use jupytext to generate jupyter notebooks. For us, this has the advantage of being more testable and reviewable. From the Documentation Contributor Guide

• All documentation should be a .md file or a .py file in the percent format file (this will generate to .ipynb for consumption)
  • Do not update .ipynb files directly. These are meant for consumption only and will be overwritten
• The code should be able to execute one time in a reasonable timeframe, our goal is to run this in build pipelines
  • Short term, before we have it in our build pipelines, please run it manually with any big changes and check there are no errors
  • Currently, run: jupytext --execute --to notebook ./doc/demo/*.py then jupytext --execute --to notebook ./doc/code/*.py
  • Soon this will be: pre-commit run jupytext --all-files
  • Please do not re-commit updated generated files if nothing has changed

Tests

• no new tests required
• new tests added
• existing tests adjusted

Documentation

• no documentation changes needed
• documentation added or edited
• example notebook added or updated

[github-actions]

Test Results

114 tests  ±0   114 ✅ ±0   14s ⏱️ -1s
  1 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit c32dc81. ± Comparison against base commit 9cfe4c3.

♻️ This comment has been updated with latest results.

[romanlutz]

Thank you for figuring out the doc tests!