Set up GitHub actions for build

[rwegener2]

What is the current state?

This issue addresses bumps in the workflow for deploying the jupyter book. Right now the book is deployed usingghp-import which adds changes to a a branch called gh-pages when a user runs the ghp-import command on their computer.

What is the problem?

Use of ghp-import means that a user must manually build and deploy the website after a PR to main has been approved. This is a step that could be automated and could also cause issues with the build if someone tries to build and deploy the new change that wasn't the contributor and their environment is not in sync.

What is the ideal end state? Is there a solution yet? (optional)

It would make for a smoother contribution process if docs were build and deployed automatically when new code is merged to main. Github actions can be used for this.

Open questions:

• right now the contents of _build is not present in the main branch, only the gh-pages branch. Do we want the raw HTML in the main branch, or should we keep that in a separate branch?