Add Pixi task for running code in the docs

[VeckoTheGecko]

What version of Parcels are you running?

main

Is your feature request related to a problem?

In the documentation, we have code in Markdown files that is run during the doc build (and fails the doc build if the code fails).

Using pixi run doc when updating this code makes for an annoying debugging cycle. It would be good to have a pixi task allowing running on a per file level.

Describe the solution you'd like

Look into the tooling, add another Pixi task

Describe alternatives you've considered

No response

Additional context

No response

[VeckoTheGecko]

Ended up hitting a bit of a dead-end here , and reached out to the Scientific Python community asking about a good way to go about this

What's the easiest way to run all code blocks in a Markdown file to make sure that the code passes? I'm using MystNB and have markdown files like

---
file_format: mystnb
kernelspec:
  name: python3
---

# Some test

'''python
print("some code that I'm updating and want to test")
'''

But looking through all of the MystNB docs I can't find any utils that allow the testing of files (or running of isolated files). https://myst-nb.readthedocs.io/en/latest/docutils.html allows the building of files, but if the code fails it just generates the HTML with traceback instead of erroring out.

I did a bunch of googling ("how to run jupytext files?", "how to run markdown files with python codeblocks?") with no luck

Doing a full sphinx build --html docs docs/_build/html everytime is quite intense

-https://discord.com/channels/786703927705862175/1151161614150680586/1498987193157550181

Will submit a PR if something comes up. For the timebeing I think working in a .py file and copying across is the best option