Update Snyk vulnerabilities in documentation

[owenlittlejohns]

Jira Issue ID

N/A

Description

I was in the Snyk UI and spotted harmony-py has a critical vulnerability in requirements/example.txt. This PR addresses the vulnerability by updating the dependencies for the notebooks in the examples directory. I also bumped the requirements in requirements/docs.txt, as there was a medium severity vulnerability there (tornado via nbconvert).

I checked things still worked by running the notebooks in the examples directory. Most ran, but there were a couple of exceptions:

• job_stac.ipynb couldn't find pystac.STAC_IO, so I changed that to pystac.stac_io, which seemed to work.
• The helper.show_results in basics.ipynb failed for a bunch of requests that were getting NetCDF-4 files out of HGA. I fixed this by forcing all the requests to give GeoTIFF outputs.
• There were some requests made to the Swath Projector that failed message validation. I thought Leo wrote a ticket for this, but can't find it in the DAS backlog. Anyway - that's not an issue with dependencies, but with the service itself.
• I was lazy and didn't try the in-region parts of the notebooks.

For the Sphinx documentation I had to tweak a method documentation string to make it all run again.

Local Test Steps

For requirements/examples.txt:

• Pull this branch.
• Create a new Python environment (via conda or pyenv) and pip install requirements/example.txt.
• Start a Jupyter notebook server (jupyter lab).
• Run through the notebooks in the examples directory. Checking basics.ipynb is probably a good one, as it uses a lot of the functionality. Similiarly, the job_stac.ipynb is a good test of pystac and intake-stac.

For requirements/docs.txt:

• Pull this branch.
• Create a new Python environment (via conda or pyenv) and pip install requirements/docs.txt.
• Navigate to the docs directory.
• Run make html - this should complete successfully.
• Open the docs/_build/html/index.html file in a browser. It should look like some shiny Sphinx-generated documentation.

PR Acceptance Checklist

• Acceptance criteria met N/A
• Tests added/updated (if needed) and passing N/A
• [x] Documentation updated (if needed)

[owenlittlejohns]

Quick update - I was getting failing builds because I updated the progressbar2 dependency in requirements/docs.txt, but another version was present in requirements/core.txt. I've updated both places, and verified the tests still pass (locally at least)