Add ODC community support generic Jupyter Hub setup to cluster as a quick-start

[woodcockr]

No description provided.

[woodcockr]

@chriscmorgan and I have agreed to tackle this one. A key principle is to keep it as simple as possible to minimise ODC community maintenance whilst demonstrating the general approach used so people can get started on their own deployment. It is not intended as a production deployemnt.
Intended feature set is:

• Using the opendatacube/jupyterhub image with jupyter labs
• Lifecycle hook to clone sample notebooks
• github auth
• Dask - on LocalCluster only, not centralised nor dask-kubernetes as these are advanced features with more management involved
• No SPOT instances (related to Dask on local node)
• User nodes for the jupyter-notebook-singleservers and ASG: demonstrates how to separate these from other nodes and allows for them to have an appropriate EC2 instance type.

We may revisit the dask and SPOT aspect later but really just trying to keep this maintainable on the ODC volunteer model.

We are not sure yet if we can use the helm charts that are available, they tend to be organisationally specific but we will look to see if ODC ones can be developed and be shared by multiple organisations.