Add workload force clean option

[sfoslund]

Consider adding an option to remove all old workload/pack installation records. Users can run into issues and want this functionality during previews where a workload is renamed and as a result cannot be uninstalled due to being unrecognized by the resolver.

[sfoslund]

@marcpopMSFT did you assign this to me because we decided we want this change or was this assigned for triage?

[marcpopMSFT]

@Redth Will mentioned that ya'll might be adding a clean option to maui check that would help here. We've seen a lot of preview to preview upgrade issues and this was one option we thought of to help with that but a maui check clean might help as well.

[Redth]

@marcpopMSFT i haven't gotten around to it yet, but I did create a .ps1 script to do this. It might be better this way so users can tell what it's going to do / doing instead of a more ambiguous clean option on Maui-check itself.

https://github.com/Redth/dotnet-maui-check/blob/main/Clean-Old-DotNet6-Previews.ps1

[marcpopMSFT]

Options for clean:

• Rollback to baseline manifest
• Clean out empty manifest folders (should this be part of repair)
• Clean out extra files in the manifest folders
• Clean out installation records (how would this work with VS + SDK)
• Clean up installed packs (similar question around msis and VS)

[KieranFoot]

NOTE: This does not work with dev packages as for some reason their signatures are checked before any attempt to remove them is made. This is the same for dotnet workload uninstall and since MS makes no effort to make sure all dependencies exist in the DEV repo, or that they're published in any kind of reverse dependant order, workload updates and installs for dev packages regularly fail and render my development machine unusable, since there is no way to remove or even roll back the offending workloads.