DO NOT MERGE: ADD: Add more robust build deploy workflow

[mgrover1]

Closes #50

@kmuehlbauer - this runs myst execute which will actually run the notebooks 👍

[github-actions]

👋 Thanks for opening this PR! The Cookbook will be automatically built with GitHub Actions. To see the status of your deployment, click below.
🔍 Git commit SHA: 3fcbdd6
✅ Deployment Preview URL: https://openradar.github.io/erad2024/_preview/54

[kmuehlbauer]

@mgrover1 That's great!

To enable building the docker container in pullrequests, I've added build-book-pullrequest.yaml in #31. This is the failing CI run in this PR.

We might just fix the current build-book and build-book-pullrequest with the changes needed for getting the new myst workflow to re-enable the former workflows.

Also you'll need to fix the Py-ART error which surfaced here (get_cmap or something).

[mgrover1]

Thanks @kmuehlbauer - I have a fix in for Py-ART 👍

ARM-DOE/pyart#1614

Waiting for CI to fully pass, then I will merge and release a new version!

[kmuehlbauer]

Although this is green, it didn't test the new workflow. I'm working on a general fix, please do not merge!

[kmuehlbauer]

@mgrover1 We might have to revisit the approach from #57 and #61 to possibly move myst build from the container back to GH Actions. That we we would not need the additional dependency to nodejs within the container. We would only need to copy the created notebooks from inside the container to outside. We might even get the folder mapping correct to have inside==outside somehow.

I'm going to close this one now.