Explore using self-contained Pluto notebooks for documentation

[seabbs]

     > i.e do we really need to support this workflow?

I haven't done this... but an option is to stop using a development approach to EpiAware for the pluto based showcases and just install EpiAware from main. Additionally, if we want we can pin the dep versions using Pkg rather than relying on finding a local path to the docs env.

The main downside is that a change to EpiAware in a branch will no longer be represented in the output of the pluto notebook. The main upside would be that each pluto nb we use will be portable; you could download it by itself and it will run locally for you from the Pluto interface without needing to install EpiAware or any of the deps.

Originally posted by @SamuelBrand1 in #395 (comment)