Guide to move dependencies from root project to modules need them

**Is your feature request related to a problem? Please describe.**
In multi-module projects that I didn't do in the first place, someone defined every dependencies in the gradle of root project instead of the module which is actually needs them.
I'm always frustrated when finding which modules used the dependencies because in the report, it only says which modules not use them

Example: In these modules A, B, C, D. Among them, B is the only one use the dependency defined in the root gradle.
In order to know it, in the report, I have to check in turn
A doesn't use it
B uses it
C doesn't use it
D doesn't use it

then move dependency from the root to B

It would be great if the report could guide me to move dependencies from root project to modules need them.

Start by examining how the dependency report identifies dependencies declared in the root project and how it reports module usage. Reproduce the A/B/C/D example, then define the report guidance needed to identify the consuming module and confirm that the result clearly recommends moving the dependency to that module.

Written by the indexing model from the issue text.