Update the jupyter labextension list compat message

[jtpio]

References

Currently running jupyter labextension list will suggest using the jupyter labextension update --all command to update extensions when it finds compatibility issues:

   The following extensions are outdated:
        jupyterlab_pygments
        @jupyter-widgets/jupyterlab-manager
        @voila-dashboards/jupyterlab-preview

   Consider running "jupyter labextension update --all" to check for updates.

However the jupyter labextension update command is now deprecated and will be removed in the future:

• Deprecate managing source extensions with jupyter labextension #12386
• Drop managing source extensions with jupyter labextension? #11336

Code changes

Update the message printed in the terminal to not suggest using this command.

User-facing changes

Users listing extensions should not see jupyter labextension update --all anymore.

Backwards-incompatible changes

None

[jupyterlab-probot]

Thanks for making a pull request to jupyterlab!
To try out this branch on binder, follow this link:

[jtpio]

We might want to backport this to 3.6.x as well.

[fcollonval]

Thanks @jtpio

[jtpio]

@meeseeksdev please backport to 3.6.x

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 3.6.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 2715840f904373642a05dc8126a9d8fa0fa91467

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #14680: Update the `jupyter labextension list` compat message'

4. Push to a named branch:

git push YOURFORK 3.6.x:auto-backport-of-pr-14680-on-3.6.x

5. Create a PR against branch 3.6.x, I would have named this PR:

"Backport PR #14680 on branch 3.6.x (Update the jupyter labextension list compat message)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.