Invest in .NET SDK quality

[marcpopMSFT]

We did an internal exercise to list out and prioritize a set of quality related investments we want to make over the next few months and years for the .NET SDK. I have tried to join the various items together into the below set of categories that bubbled to the top of the list. We'll also use feedback from the ongoing survey to inform some of these investments.

• Threat Model updates
  In recent years, we've done threat reviews of new features like Workloads or the .NET Acquisition extension in VS Code. Let's revisit the threat models for the .NET SDK and Template engine to update them for any new behaviors that might have been missed, identify threats, and apply mitigations.
• Review and improve the dotnet CLI
  • Review the CLI feedback from the SDK survey
  • Do a pass over all CLI commands focusing on the parameters and consistency
  • Investigate improvements we can make to the CLI experience
  • Investigate code cleanup we can make to our CLI code construction
• VS insertion process
  The process today is very different than how most other teams insert components into VS. As such, we've developed a completely separate set of insertion tooling that has to be maintained.
  • Move the setup authoring generation into the .NET SDK repo
  • Swap out the custom tooling in favor of the common tooling
• .NET install tool uninstall behavior
  The VS Code acquisition extension can install .NET runtimes and SDKs but today will never remove them.
  • Expand the options through the commandpallet for removing sdks and runtimes not currently associated with existing extensions.
• Improve test coverage (for VMs)
  • We now have a VM testing process for Admin testing for workloads. Invest in additional scenarios to give us more confidence when making changes