moves all environment info into a single environment.yml file that just uses conda and allows for more recent versions of Python to be used
adapts the GitHub actions workflows to use the updated environment file
renames the GitHub actions workflows to build.yml and deploy.yml to simplify and make it clear what they do
limits the build workflow to just building the JupyterBook
limits permissions a bit to only what's needed to deploy and only in the deploy workflow
updates the submission guidelines accordingly
Alternately, we could use a requirements.txt file, but the environmental.yml file allows use to specify a bit more information about the environment. It's also possible to use both, but I think that's a bit confusing and potentially creates more room for error.
Specifically, this PR:
environment.ymlfile that just uses conda and allows for more recent versions of Python to be usedbuild.ymlanddeploy.ymlto simplify and make it clear what they doAlternately, we could use a requirements.txt file, but the environmental.yml file allows use to specify a bit more information about the environment. It's also possible to use both, but I think that's a bit confusing and potentially creates more room for error.