Modernize torchsharp infrastructure

[ericstj]

In looking at Torchsharp's build I had a few thoughts for improvement.

• Evaluate using arcade and provided build templates.
• Remove as much as possible from the YML and have it be part of the local build scripts so that it's easier to repro things that are hit by the official build.
• Remove use of the nupkgproj and instead pack from the CProj projects where possible
• For the remaining nupkgproj have them use the Microsf.Build.NoTargets SDK to avoid C# specific targets.
• Add all projects to the SLN, and control the pack behavior with IsPackable conditions rather than conditions in a project

  TorchSharp/pkg/pack.proj

  Line 4 in 077780d

  <PackProject Include="**\libtorch-cpu.nupkgproj" Condition="'$(IncludeLibTorchCpuPackages)' == 'true'" />

• Adopt package readme's following a similar convention to dotnet\runtime.

[alinpahontu2912]

@ericstj Thank you for reporting the issue regarding the modernization of TorchSharp's infrastructure! Your suggestions about using arcade for build templates and streamlining the YAML configurations are certainly valuable. It's been a while since this was raised, and TorchSharp has evolved significantly in the past two years.

Could you please let us know if this issue is still relevant or if any of your suggestions have been addressed in recent updates? If the issue still stands, any updated information you can provide would be greatly appreciated. Thank you for your contributions to the project!