[release/9.0.1xx] Workloads: Support VS component IDs

[joeloff]

Description

Visual Studio publishes a component catalog for extension developers. .NET option workloads do not currently follow the naming convention.

• Refactored the logic for generating safe IDs into the WorkloadId struct to ensure a single source of truth.
• ShowMissingWorkloads task will set VisualStudioComponentId to use the new component prefix. 'VisualStudioComponentIds` will include the old and new component IDs
• Added wasm-tools-net8 to the set of known workload IDs.

Testing

Additional unit tests to verify the changes to WorkloadId. Previous changes for dotnet workload list continue to return the expected results. Will likely require additional validation once we have a build with all the workload changes and the CLI with this change inserted into the same VS.

Risk

Low - if WASM/Maui does not switch to using the new workload IDs it may degrade the IPA experience.

[joeloff]

@dsplaisted I modified the GetValuesCommand. For missing workloads, we can have metadata values that include a ";". If we don't escape that, the WriteLinesToFile task ends up writing two lines instead of just one:

microsoft-net-sdk-missingtestworkload   Microsoft.NET.Component.sdk.missingtestworkload microsoft.net.sdk.missingtestworkload
Microsoft.NET.Component.sdk.missingtestworkload

I made this a configurable option in case turning it on by default impacted other tests. Seemed like the less intrusive option

[drewnoakes]

LGTM though I can't see all the consequences of this change.

[joeloff]

LGTM though I can't see all the consequences of this change.

Thanks, I'll be doing some testing on this build and setting up a project that injects additional, non-existing workloads to see how VS responds.