Only include dependencies from the csproj in the project_path to review

[Critical-Impact]

The PR adjusts the way that Plogon collects the nuget packages that are listed to review. It does this by restoring all the packages but only adding the ones that are collected from the csproj within the project_path provided by the plugin. If no project_path is provided in the plugin's manifest, it'll include every package as it was doing before.

The primary use case for this is when you have a structure like this

PrimaryPlugin/PrimaryPlugin.csproj - Only includes TertiaryLibrary.csproj
TertiaryLibrary/TertiaryLibrary.csproj
NotIncluded/NotIncluded.csproj

Before the changes it'd pick up the nuget packages on all 3 csproj files, but after it only picks up the nuget packages on PrimaryPlugin and TertiaryLibrary.

[goaaats]

Is there a reason we are still downloading dependencies from lockfiles outside the project path altogether? Is it necessary for the build? At the very least, I think we should not download things we aren't also tracking, since that defeats the purpose of it a little bit IMO. Code looks good otherwise!

[Critical-Impact]

Sorry, missed this comment
From what I recall(and I can give it another go) removing the other dependencies appeared to break the build process even if they weren't used in the final artifact. It might be possible to have it not download them, I'll look into it