Improve GitHub Actions

[rcf49]

• Separate steps into separate jobs, as it makes sense. For example, have a build job to create the environment, and then a job for running the commands. And then a final job for pushing updates.
  • build
  • test
  • deploy
• Default will run jobs in parallel. But can make jobs dependent on each other: https://docs.github.com/en/actions/using-jobs/using-jobs-in-a-workflow
• Create GitHub issue to group together the automated pushes. Then update the commit message to include that number.

[rcf49]

1. Created separate jobs for running and testing python, and then another set of jobs for building and deploying the GitHub Pages web page
2. The jobs are dependent on each other, so they will not run in parallel
3. Created issue #5 in order to track all future pushes/commits automatically made in a GitHub Action