Speed up lock file update when path dep lock file gets updated

• I have searched the issues of this repo and believe that this is not a duplicate.
• I have searched the FAQ and general documentation and believe that my question is not already covered.

Feature Request

I use poetry in a python monorepo, where the packages in it depend on each other using a path dependency.
For example package C -> B -> A, where folderstructure is
root
|- packageA
|- packageB
|- packageC

If I add a dependency to A, it (as expected) does not get added to package B, nor C's poetry lock files.
The only way I've found to update the lock files of B & C is by running poetry update within B, and then within C.

With many such projects, and each with many dependencies, this can become very slow (which I know is because of the PyPI way of dependency specification).

However, as this happens all within a single repo, where the dependency of C->B->A are all specified by relative paths, would it be possible

• that a poetry check or poetry lock --no-update inspects the lock file of A (just as it could inspect the pyproject.toml of A)?
• to run a poetry update on B which will only inspect the (new) dependencies of A?

Start by reproducing the packageA → packageB → packageC path-dependency layout described in the issue and compare the behavior of poetry check, poetry lock --no-update, and poetry update. Determine how lock files are currently refreshed across path dependencies; done should mean dependent projects can incorporate updated transitive dependencies without repeatedly resolving unrelated packages.