Use binderbot to ensure notebook reproducibility

My understanding is that the notebooks contained in the VEDA docs are rendered from committed cell outputs. We could consider instead rendering the Quarto book by executing each notebook during the build process on the VEDA hub to ensure continued reproducibility as software versions change (xref https://github.com/NASA-IMPACT/pangeo-notebook-veda-image/pull/31#issuecomment-2605315151). More specifically, we could follow the approach that Project Pythia developed for their cookbooks which uses binderbot and some re-usable but custom GitHub actions. Here's a summary of their approach from Brian Rose's Pangeo showcase presentation last fall:

Start by reviewing the committed notebooks in the VEDA docs and the linked Project Pythia cookbook-actions build-book.yaml. Compare that workflow with the current VEDA docs build process and determine how binderbot would run notebooks on the VEDA hub. Done means the book build executes the notebooks and verifies reproducible outputs as dependencies change.