Tweak workload build to use _GenerateMsiVersionString target

[steveisok]

Replaces GenerateVersions that wasn't quite accurate enough for what we need

[ghost]

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Replaces GenerateVersions that wasn't quite accurate enough for what we need

Author:	steveisok
Assignees:	-
Labels:	area-Infrastructure-libraries
Milestone:	-

[steveisok]

official build successful

https://dev.azure.com/dnceng/internal/_build/results?buildId=1430904&view=results

[radical]

re:WasmBuildTests workload installation failure, not sure why exactly it is failing. I have seen that before on windows, but that was when you would have two packs dir with the same name differing only in case. Maybe the tool is getting confused somehow?

Also, note that even after the rollback, there is a /__w/1/s/artifacts/bin/dotnet-workload/packs/Microsoft.NET.Runtime.Emscripten.2.0.23.Sdk.linux-x64 directory left. So, that might be the one for which it got confused, and that tracks with the pack that it failed at.

I'll wait to see if the re-run also fails.

[steveisok]

/backport to release/6.0

[github-actions]

Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1364843150

[github-actions]

@steveisok an error occurred while backporting to release/6.0, please check the run log for details!

Error: @steveisok is not a repo collaborator, backporting is not allowed.

[lewing]

/backport to release/6.0

[github-actions]

Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1364857178

[lewing]

This looks like what we discussed since using the arcade target was not possible. Should we open an issue in arcade as well.