Show what dep brought in a dep, also the path to it

[DarthHater]

To help devs figure out how to remediate, it was suggested to add the:

• list of deps that require the dep
• the path to the dep

This gives a developer a lot of information to go on to figure out why something was brought in.

This pull request makes the following changes:

• Adds fields for what required a dependency, populates them as we parse the list from read-installed
• Adds a field for the realPath to the dependency, populates it
• Passes both the read-installed coordinates and ossindexserverresults to Audit, and merges them
• Outputs the dependency information:

cc @bhamail / @DarthHater / @allenhsieh / @ken-duck

[bhamail]

+1. I added some unit tests in a separate PR. Please give that PR a quick look.

I'd be happy to have any feedback on that PR. Also, would like to merge that PR either to this PR or later to master.

[bhamail]

FWIW, to assist myself in collecting a clue, I added some unit tests around this here.