improve QUEST documentation

[JessicaS11]

Looking through our docs page, it would be great to add some more QUEST documentation/clarity. Specific tasks/ideas:

• Add uml generation for QUEST (via add quest to pyreverse uml generation #498)
• Clarify the QUEST-icepyx relationship in the API docs (perhaps giving QUEST its own API page?)
• Mention QUEST in the intro to icepyx docs (via Added a brief mention to QUEST in icepyx docs intro. #514)
• provide a detailed guide for adding a dataset via QUEST
• Add a tile for QUEST on the home page! (via include quest tile in index.rst #497)
• Add a link to AGU presentation/JupyterBook (and mint DOI for presentation)

[zachghiaccio]

Going to start by working on the last checkbox - I think we discussed giving the Jupyterbook a Zenodo link.

Does icepyx have a Zenodo community ID? I could upload the notebook through my personal account, though it might be preferable to have a group Zenodo.

[JessicaS11]

Resource for building a class, cell by cell, in a JupyterNotebook, for the detailed how-to-add-a-dataset example.