Fix issues in DependencyInsight recipe

[mike-solomon]

Right now, the data table produced by the DependencyInsight recipe results in a massive amount of irrelevant/duplicate data:

There are two primary issues:

1. When multiple different dependencies bring in the same thing (e.g., jackson-core), a new entry is added - but we are not recording the name of the dependency which actually brings it into the data table. This makes it difficult to see what's actually going on and diminishes the use of the table.
2. On top of the above issue, the recipe searches through dependencies transitively - so you can end up where you have only one or two dependencies in the project but those dependencies depend on something else that depends on something else and then you end up with 50 rows all depending on the same thing as you trace through all of the projects. We should consider some type of de-duplication here to make this table more relevant.

[okundzich]

@sambsnyd I think you were making changes to this area