Introduce Workload Clean: Garbage Collection Component

[nagilson]

What's this?

Resolves #19603
Doc: #30480

• Adds PART ONE of dotnet workload clean:
  (So not the stuff in 2) shown below.)

• Make workload list show all VS workloads regardless of feature bands.

• Workload --info now correctly shows msi or filebased install type.

• Fixes Incorrect customer facing logging messages.

• Refactor MSI Garbage Collection into separate functions to make it easier to use

• Note that workloads will still appear after workload clean --> workload list, but not for workload clean --all, because we don't remove the workload installation record itself in GC. The old GC also does not remove workload installation records for workloads of uninstalled featurebands. To do this, we would need the manifest or some sort of history ledger to map N-1 packs to a workload id. Or maybe we could include the workload id in the workload pack records, but not sure if we want to do that.

• Evidence of VS Workload Behavior:
  

• Evidence of MSI Clean up:
  
  
  

• Shows that MSI clean up works for older feature bands:

C:\Users\WDAGUtilityAccount>dotnet --info
.NET SDK:
 Version:   7.0.103
 Commit:    276c71d299
...

C:\Users\WDAGUtilityAccount>dotnet workload install wasm-tools

The machine has a pending reboot. Installation will continue, but you may need to restart.
...

Successfully installed workload(s) wasm-tools.


C:\Users\WDAGUtilityAccount>dotnet workload list

Installed Workload Id      Manifest Version      Installation Source
--------------------------------------------------------------------
wasm-tools                 7.0.3/7.0.100         SDK 7.0.100
maui-windows               7.0.59/7.0.100        VS 17.4.33403.182

...


--> Then in an 8.0 terminal:

PS C:\Users\WDAGUtilityAccount\sdk> dotnet workload clean --all

--> Then back to 7:

C:\Users\WDAGUtilityAccount>dotnet workload list

Installed Workload Id      Manifest Version      Installation Source
--------------------------------------------------------------------
maui-windows               7.0.59/7.0.100        VS 17.4.33403.182

[2023-02-09 16:25:41.122] [00001D28] Microsoft.Maui.Resizetizer.Sdk (7.0.59) will not be removed because other dependents remain: VS.{AEF703B8-D2CC-4343-915C-F54A30B90937}.
[2023-02-09 16:25:41.123] [00001D28] Microsoft.Maui.Sdk (6.0.552) will not be removed because other dependents remain: VS.{AEF703B8-D2CC-4343-915C-F54A30B90937}.
[2023-02-09 16:25:41.124] [00001D28] Microsoft.Maui.Sdk (7.0.59) will not be removed because other dependents remain: VS.{AEF703B8-D2CC-4343-915C-F54A30B90937}.
[2023-02-09 16:25:41.124] [00001D28] Microsoft.Maui.Templates.net6 (6.0.552) will not be removed because other dependents remain: VS.{AEF703B8-D2CC-4343-915C-F54A30B90937}.
[2023-02-09 16:25:41.124] [00001D28] Microsoft.Maui.Templates.net7 (7.0.59) will not be removed because other dependents remain: VS.{AEF703B8-D2CC-4343-915C-F54A30B90937}.

• Show that VS workloads across versions are displayed:

PS C:\Users\source\repos\sdk> dotnet workload clean --all
Workload 'maui-windows (VS 17.4.33213.308, VS 17.4.33205.214)' was not removed because it is installed and managed by Visual Studio. Please uninstall this workload through Visual Studio to fully remove it.
Workload 'maui-ios (VS 17.4.33205.214)' was not removed because it is installed and managed by Visual Studio. Please uninstall this workload through Visual Studio to fully remove it.
Workload 'ios (VS 17.4.33205.214)' was not removed because it is installed and managed by Visual Studio. Please uninstall this workload through Visual Studio to fully remove it.

• Updated test plan for MSIs for vendors.

(Note that I added this into my own copy of main so it won't go into prod.)

Should

1. Run garbage collection for the SDK feature band under execution
   2) Restore Manifests to 'fresh' state, to whatever baseline manifests were initially shipped with the current SDK feature band, however, including edits that VS made to said manifest, assuming a ledger is available. (Daniel is working on the ledger.)

Add dotnet workload clean --all:
Should

1. Remove ALL CLI installed workloads for the SDK feature band under execution and for all feature bands of the SDK below the current version of the SDK. It should also give a message for VS installed workloads and say that these workloads weren't installed because they are managed by VS.

Note that this is different from running dotnet workload uninstall en masse. Workload uninstall needs the manifest to know what has been orphaned.

2) Restore manifests to 'fresh' state, like above, but for all lower SDK feature bands if possible. (They may not have a ledger available.)

Not in this PR:

Make workload list show all workloads regardless of feature band.

[nagilson]

@dsplaisted @joeloff I have responded to all feedback, including making it work for > feature bands. If we would like to revert that part, it is a simple commit revert. Thank you.

[nagilson]

@dsplaisted I have responded to all of the feedback, thanks for taking a look. I know you still need to look @ the tests.

[dsplaisted]

Looks good.

[nagilson]

@marcpopMSFT pls merge on red, arcade outage seems to be blocking this pr

[marcpopMSFT]

Do we have a link to a known outage we can ping them on?

[nagilson]

I believe it's fixed now, so no action needed :)