Production Notebooks

Work with Adam.Avison to ensure AIV teams understand how to deploy components to AA0.5 production systems, and then run appropriately configured notebooks to conduct observations.

(NB: this may split into two features, one for #! about deploying stuff and then another feature about managing the notebooks for ST and Adam.)

Thoughts from Adam.Avison on the purpose of `ska-jupyter-scripting`:

**
My hope for ska-jupyter-scripting is as follows:
At some point in PI23, there should be ~5 Notebooks in the notebooks/observing/ directory. # MID Raw visibility data capture aka Interferometry 

1. LOW Interferometry
2. LOW PST
3. MID Holography (maybe)
4. MID global pointing model update observation.
5. (Maybe) MID 5-point scan but really that should be part of 1.

When we make them work properly and have a MID and LOW chart/values pair with all the right versions of stuff, AIV, SciOps, SystemScience can do the following: # boot up binderhub and run through these examples.

1. within binderhub or a branch of the repo, make and test their own versions of the notebooks.
2. copy the examples + charts (if they don't have their own) in to their environment (ITF etc) and use these as a basis for doing what they need to do.

With System Team having made the pipeline jobs have a MID / LOW split and setting up ska-jupyter-scripting so it has a MID and LOW chart. I think we're most of the way to doing this. I just need multiple people to work on making those example scripts actually work and maintain them as new SW vers are released