leap: Bump pangeo notebook version

[jbusecke]

Unsure if I bumped the version in all the right places. Particularly I am not sure what the tag here does.

[github-actions]

Merging this PR will trigger the following deployment actions.

Support and Staging deployments

Cloud Provider	Cluster Name	Upgrade Support?	Reason for Support Redeploy	Upgrade Staging?	Reason for Staging Redeploy
gcp	leap	No		Yes	Following helm chart values files were modified: common.values.yaml

Production deployments

Cloud Provider	Cluster Name	Hub Name	Reason for Redeploy
gcp	leap	prod	Following helm chart values files were modified: common.values.yaml

[github-actions]

🎉🎉🎉🎉

Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/5403107197

[consideRatio]

Unsure if I bumped the version in all the right places. Particularly I am not sure what the tag here does.

I'm not 100% confident myself, but when automated tests are running - I think that image will be used to verify that a server can startup properly.

[jbusecke]

Saw some errors in the deployment. Is that a concern?

[jbusecke]

FWIW our hub shows some display errors, e.g. in the tabs of the dask-extension

Not sure this is related, but wanted to document.

[consideRatio]

The staging hub deployed but the test-startup of a user server failed. It can happen if a new node had to start and image was slow to pull or similar. I tested myself and it works, so I'm deploying to the production hub now manually.

What you observe in the jupyterlab extension for dask is perhaps related to upgrading the images and the software in them. I'd guess either jupyterlab or the labextension was upgraded and there was a regression in the UI that probably relates to both codebases.

[consideRatio]

@jbusecke successfull deploy to prod, and i could start a server etc using the latest image bump!