Use container directly with Coiled

[jrbourbeau]

Since a docker image is already being built, there's no need to worry about using a Coiled software environment (those are just a simple way for users not familiar with docker to build a docker image). Instead, we can just pass the container directly to coiled notebook start and coiled.Cluster.

[matthewhanson]

@jrbourbeau is there any performance benefit to using the coiled software environment and is a new image pulled everytime if you do use a software environment (even if the tag hash hasn't changed)?

[jrbourbeau]

Both manual software environments and container= have the same performance and will always pull in whatever the latest tag is at the time cloud VMs are spinning up.

Using container= avoids the need to maintain a separate software environment. It also avoids the need for people to create the software environment in their own Coiled accounts if they want to run these notebooks after the workshop.