Test.Utility has too many dependencies, making tests requiring compilation of the whole tree

[nkolev92]

Test.Utility depends on:

    <ProjectReference Include="..\..\..\src\NuGet.Clients\NuGet.CommandLine\NuGet.CommandLine.csproj" />
    <ProjectReference Include="..\..\..\src\NuGet.Clients\NuGet.PackageManagement.VisualStudio\NuGet.PackageManagement.VisualStudio.csproj" />
    <ProjectReference Include="..\..\..\src\NuGet.Clients\NuGet.VisualStudio.Common\NuGet.VisualStudio.Common.csproj" />

    <ProjectReference Include="..\..\..\src\NuGet.Core\NuGet.Commands\NuGet.Commands.csproj" />
    <ProjectReference Include="..\..\..\src\NuGet.Core\NuGet.Resolver\NuGet.Resolver.csproj" />
    <ProjectReference Include="..\..\..\src\NuGet.Core\NuGet.PackageManagement\NuGet.PackageManagement.csproj" />

This is probably like 30 projects.

NuGet.Versioning does not have any dependencies.

NuGet.Versioning.Test for example, depends on Test.Utility, which effectively means, NuGet.Versioning.Test, depends on 31 projects.

This is unnecessary, and makes test running slower. We need a better pattern than just having everything dependency on Test.Utility.

Ideas:

• Compile the utility code into every test project.
• Break down the Test.Utility into more than 1 project.
• Don't reference Test.Utility in every project.

[nkolev92]

cc @kartheekp-ms Not sure which discussion this falls into, but this is tech debt too.