Should conda-store jupyterlab extension be re-enabled once it supports JupyterLab 4?

[krassowski]

Context

Following the issue #2181 the conda-store extension for jupyterlab was disabled in nebari. Once jupyterlab-conda-store support for JupyterLab 4.x (which was merged in conda-incubator/jupyterlab-conda-store#34) is released, should default image of nebari include jupyterlab-conda-store again, or should it be an optional extension which deployments managers can install?

If this is to be an optional extension, addressing #2299 might be of a higher priority.

Value and/or benefit

Users would not need to open a new page to modify their environments.

The cost of making sure that jupyterlab-conda-store supports latest JupyterLab version does not appear high to me, but I appreciate that others may disagree. I don't think it is high because excluding dependency bumping and linting, there was only one line of code change required to transition between major JupyterLab versions from 3 to 4:

-      mainMenu.addMenu(condaStoreMenu, { rank: 1000 });
+      mainMenu.addMenu(condaStoreMenu, true, { rank: 1000 });

This is because most of the code is isolated in conda-store package itself.

Anything else?

No response

[Adam-D-Lewis]

I assume we would want to re-enable the extension in Nebari once it supports Jupyterhub 4