Investigate improving the versioning for previews to reduce churn

Today there are multiple steps required when going from preview to preview as outlined in https://github.com/dotnet/workload-versions/pull/599

For the workloads-versions repo, emsdk uses a stable transport package so never has to update it's package id. We could model that for the maui workloads as well.

For VS, the maui workloads use a stable package id throughout previews which avoids any extra changes to the vsmanproj or elsewhere. We could do something similar to mono and emsdk which today require updating those prior to running the workloads insertion pipeline.