slap add --upgrade can show inconsistent version warning

[NiklasRosenstein]

What is also surprising is that although the newer version got installed by the first run already, but Slap still finds the old version to write into pyproject.toml.

$ slap add slap.core.cli --upgrade
(venv-aware) a virtual environment is already activated (/Users/niklas.rosenstein/Library/Caches/pypoetry/virtualenvs/my-package-FPuO3UBk-py3.10)
Installing PypiDependency(name='slap.core.cli', version=VersionSpec(''), source=None, extras=None, python=None, markers=None, hashes=None)
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
my-package 0.1.0 requires slap.core.cli<0.2.0,>=0.1.3, but you have slap-core-cli 0.2.0 which is incompatible.
Adding PypiDependency(name='slap.core.cli', version=VersionSpec('^0.1.3'), source=None, extras=None, python=None, markers=None, hashes=None)

$ slap add slap.core.cli --upgrade
(venv-aware) a virtual environment is already activated (/Users/niklas.rosenstein/Library/Caches/pypoetry/virtualenvs/my-package-FPuO3UBk-py3.10)
Installing PypiDependency(name='slap.core.cli', version=VersionSpec(''), source=None, extras=None, python=None, markers=None, hashes=None)
Adding PypiDependency(name='slap.core.cli', version=VersionSpec('^0.2.0'), source=None, extras=None, python=None, markers=None, hashes=None)