Dotnet list package json output implementation

[erdembayar]

Bug

Fixes: NuGet/Home#7752

Regression? Last working version:

Description

Implement Dotnet List Package Machine Readable Json Output spec (spec PR), e.g. dotnet list package --format json will give you json output.
If there any error with json generation then application will return non-zero value.
This PR also include MVC style refactoring of the existing dotnet list package to console output logic.
Here get the report model/data

NuGet.Client/src/NuGet.Core/NuGet.CommandLine.XPlat/Commands/PackageReferenceCommands/ListPackage/ListPackageCommandRunner.cs

Line 38 in 7691366

(int exitCode, ListPackageReportModel reportModel) = await GetReportDataAsync(listPackageArgs);

and it's shared by both console and json output options. So that means any existing tests like DotnetListPackageTests.cs already covers up until

NuGet.Client/src/NuGet.Core/NuGet.CommandLine.XPlat/Commands/PackageReferenceCommands/ListPackage/ListPackageCommandRunner.cs

Line 39 in 7691366

reportRenderer.Render(reportModel);

point, this reduces the need for adding many duplicate tests. Only after this implementation details diverge between them, so I added tests for json report Renderer implementation by passing report model.
I added most basic unit tests, I'll add more later if needed.

PR Checklist

• PR has a meaningful title

• PR has a linked issue.

• Described changes

• Tests

  • Automated tests added, I'll add tests after getting confirmation on my current implementation is good enough.
    • Created follow up issue for integration tests: Add integration tests dotnet list package json outputs Home#12167
  • OR
  • Test exception
  • OR
  • N/A

• Documentation

  • Documentation PR or issue filled
    • https://github.com/NuGet/docs.microsoft.com-nuget/issues/2922
  • OR
  • N/A

[erdembayar]

Json output is redirected to consoleOutput.txt file. Later this file content compared to expected output for assertion.

[nkolev92]

Just some minor comments at this point.

There are some tests failing, so approving it wouldn't help much :D

[rohitcoder]

@nkolev92 @erdembayar I wanted to check if we have the same feature but for dependency graph relation. Something like showing child dependencies in the parent (Simply a dependency relation JSON graph).

[erdembayar]

@nkolev92 Nikolche Kolev FTE @erdembayar Erick Yondon FTE I wanted to check if we have the same feature but for dependency graph relation. Something like showing child dependencies in the parent (Simply a dependency relation JSON graph).

I don't believe we have one considering this is the 1st ever json output we have. You can create a feature request here.