Migrate useful notebooks to the deployment docs repo

[jacobtomlinson]

In rapidsai/deployment#108 I copied a couple of the notebooks from this repo over into the deployment docs so that I had something to work with when updating the Sphinx theme.

As part of #197 we need to migrate the rest of the notebooks in this repo over, but those can be done in separate PRs. Not all notebooks here are in a good state, so we should just focus on migrating the ones which are up to date and confirmed to be working/useful.

My preference would be for each notebook to be placed in its own directory in the source/examples section of the deployment repo with no nesting. The notebook should probably be renamed to notebook.ipynb too so that the URL looks nice.

Any supporting files should be also placed in the directory alongside the notebook. Again ideally without any nested directories unless there is a technical reason why we need to do so.

source/examples
├── index.md
├── rapids-sagemaker-higgs
│   ├── Dockerfile
│   ├── notebook.ipynb
│   └── rapids-higgs.py
└── xgboost-gpu-hpo-job-parallel-k8s
    └── notebook.ipynb

Each notebook also needs to be added to the toctree of the source/examples/index.md file.

Once the notebook has been copied and merged it needs to be removed from this repo and replaced with a link so folks can find them again.

### Tasks
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/206
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/207
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/208
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/209
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/210
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/211
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/212
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/213
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/214
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/215
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/216
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/217
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/218
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/219
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/220
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/221
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/222
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/223
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/224
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/225
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/226
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/227
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/228
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/229
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/230
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/231
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/232
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/233
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/234
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/235
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/236
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/237
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/238
- [ ] https://github.com/rapidsai/cloud-ml-examples/issues/239

[jacobtomlinson]

Notebook migration guide

We are migrating the notebooks from this repo to the deployment docs. To get started pick any unassigned issue from the tasklist above and assign yourself. Unassigned notebooks with migrate: yes already set are the highest priority.

Decide if notebook should be migrated

For each notebook we need to assess it and decide whether we actually want to migrate it. If the notebook is very out of date or irrelevant to the state of RAPIDS today we shouldn't waste time with it and just let it be archived. Some notebooks are fully up to date (as noted by a link a green tick on the repo README) so definitely should be migrated and have already been marked as such. Others are in the middle.

Use your best judgement and add a migrate: yes or migrate: no label to the issue, if you decide no write a small comment in the issue on why it won't be migrated and then close the issue.

Test if notebook works

Run through the notebook and check that it works and the instructions make sense.

If the notebook needs some attention fix things up and get it into a good state.

Ensure notebook has good title and metadata tags in the first cell

The first cell of each notebook should be markdown and contain a descriptive title and a few sentences about what the notebook does.

This cell should also have cell tags to allow it to be organised by the notebook gallery Sphinx extension.

For example if the notebook is an HPO workflow running on Azure ML and uses XGBoost and cuDF it should have workflows/hpo, cloud/azure/ml, library/xgboost and library/cudf tags.

Remove any deployment instructions and link instead

Many of the notebooks have deployment instructions baked into them. We should remove or at least slim these down and link out to the deployment documentation pages.

For example if a notebook contains instructions on starting a Kubernetes cluster on Google Cloud that should be replaced with a callout to the GKE documentation page.

Copy notebook to deployment docs examples

In the Deployment docs repo create a new directory for the notebook in source/examples and copy the notebook into that directory. The notebook should also be renamed to notebook.ipynb to make the URL neater.

Copy any supporting files to the folder

If the notebook has supporting files such as Python scripts, Dockerfiles or any other config files also copy those into the directory. The notebook gallery Sphinx extension will list these files automatically in the sidebar and link to them on GitHub once they have been merged.

Add notebook to examples toctree

Also update the toctree in source/examples/index.md with the relative path to the notebook.

Make PR to deployment docs repo

Open a new Pull Request for each notebook so we can review them individually. Mark the PR as closing the issue in this repo associated with that notebook.