Publish SDK packages to NuGet

[Qonfused]

The current SDK is only set up for users to build against a clone of the project. This is mostly due to unresolved questions on how/whether to distribute reference assemblies generated by the MTGOSDK.Ref project, which are required runtime dependencies by the main MTGOSDK library (for reflection).

Only the MTGOSDK and MTGOSDK.Win32 libraries would need to be published to NuGet, requiring an additional pipeline for packaging the built reference assemblies.

This also requires additional infrastructure for supporting publishing and building the SDK through .NET Core.

Tasks

Beta Give feedback

1. Fix MSBuild dependency graph resolution #8
   +0
   
2. Optimize MSBuild logging and caching #9
   +0
   
3. Refactor RemoteNET projects #13
   +0
   
4. Refactor ScubaDiver project #14
   +0
   
5. Merge MTGOSDK.MSBuild and MTGOSDK.Ref projects #16
   +0
   
6. Add SourceLink support to MTGOSDK #15
   +0
   
7. Add Trimming Support #20
   +0
   
8. [MTGOSDK/Core] Refactor Compiler, Remoting namespaces #22
   +0
   
9. Refactor ScubaDiver #23
   2 of 3
   +0
   
10. Create NuGet publish pipeline for MTGOSDK
11. Add build provenance with Sigstore #19
    +0
    
12. Hook publishing to GitHub Actions CI

[Qonfused]

Reference assemblies are now merged with the MTGOSDK library and are not distributed separately (resolved in 4b26663). Transitive build targets are still bundled with MTGOSDK.MSBuild as an optional package.