Autolinking needs to be updated to process the nugetPackage objects from dependency configs

Summary

Autolinking needs to be updated to process the nugetPackage objects from dependency configs

• Need to check the nugetPackage objects for all the items and/or errors and flag them as invalid dependencies just like with projects
• Need to update getCSModules to consider nugetPackageLang of nuget package when detecting if we have C# modules (to make sure the M.RN projects are present and setting ConsumeCSharpModules)
• Generating the autolink targets needs to add package references for the modules and versions specified (don't insert if packages.config, give warning)
• The header/using/IPackageProvider lines should be processed (and inserted) just like for projects

This depends on #9576

Motivation

Enabling this support will let enable autolinking to consume nuget-based community modules.

It can also be used to add any nuget dependencies into an app project

Basic Example

No response

Open Questions

No response

Start with the dependency-config handling and the getCSModules entry point, then trace how autolink targets are generated. Check how project dependencies and errors are currently processed, and compare that flow with the requested nugetPackage handling. Done means invalid packages are flagged, C# modules are detected correctly, package references and warnings are generated appropriately, and header/using/IPackageProvider lines are inserted.