Ambiguity if the installed app is also a dependency

[unkcpz]

This is a design issue rather than a bug if a registered app is installed and it is also installed as a dependency of another app. This is now only happening on aiidalab-widgets-base.
The installed version is detected from the local repo either by version in registered list or by the version in "setup.cfg" as defined in

aiidalab/aiidalab/app.py

Line 144 in 50498b0

def installed_version(self) -> AppVersion | str:

. If another app has this app in their dependencies list, the app will be installed through pip again. It leads to two scenarios:

1. if the app is installed first (let's say AWB-2.0.0a2), the pip install of it as a dependency will override it (let's say qeapp install awb-2.0.0a1 ), which makes in the app manager the version of app shown is 2.0.0a2 which pip freeze shows the awb version in use is 2.0.0a1.
2. if the app is installed after, it will be all fine that the installed version shown in app manager is conformed with the pip list.

One option I want to propose is to prevent them from app installing other apps as a dependency, this is easy to detect by comparing the dependencies list in terms of the register app list, and in design makes a lot of sense to me. The problem is we have AWB which is going to be deprecated as an app that is a strong dependency of many other app. Removing it from the app registry will be the first step to move forward.

pinning @yakutovicha @danielhollas for comments.