Better Support for Nuget Dependencies for Binary Modules

Port of https://github.com/PowerShell/PowerShell/issues/15588

Summary of the new feature/enhancement

Powershell Package Authoring in C#/.Net is a very unsatisfying task for anything that relies on complex Nuget Packages. As an example: It's nearby impossible to get a package working on Powershell Gallery that relies on the Nuget Package of the SQL Server Driver (Microsoft.Data.SqlClient). I have to reference platform specified dll's somehow and it requires a lot of code just to get that dll working. The SQL Server Module

In addition, as a Powershell package can only have dependencies from PowershellGallery (de-facto), it's common to include the .Net DLLs in the Package, see SqlServer Module for example. If two packages include the same dll's we have a conflict. As an example, the SqlServer Module mentioned uses Newtonsoft.Json which should be fairly common to include.

Proposed technical implementation details

I'd propose to support Nuget Dependencies directly in the Manifest Files (psd1).

Start by reading the proposed support for NuGet dependencies in PowerShell module manifest files (psd1), then compare the dependency and DLL handling used by the SqlServer Module. Define how package authors would declare NuGet dependencies and how conflicting .NET DLLs should be resolved; completion requires an agreed design and corresponding implementation and tests.