Add ProductVersionSuffix to workload manifest names

[steveisok]

This change adds a prerelease label to workload manifests so that they can sit beside official ones in the dotnet sdk. For example, Microsoft.NET.Workload.Mono.ToolChain.net7.Manifest-8.0.100-alpha.1 could install alongside Microsoft.NET.Workload.Mono.ToolChain.net7.Manifest-8.0.100 and not cause conflicts.

Fixes #79086

[ghost]

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This change adds a prerelease label to workload manifests so that they can sit beside official ones in the dotnet sdk. For example, Microsoft.NET.Workload.Mono.ToolChain.net7.Manifest-8.0.100-alpha.1 could install alongside Microsoft.NET.Workload.Mono.ToolChain.net7.Manifest-8.0.100 and not cause conflicts.

Fixes #79086

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

[radical]

https://github.com/steveisok/runtime/blob/ef16a86d343e15c6ac67c5bb3eef47ff9fc1db68/eng/testing/tests.wasm.targets#L337-L338
and
https://github.com/steveisok/runtime/blob/ef16a86d343e15c6ac67c5bb3eef47ff9fc1db68/eng/testing/workloads-testing.targets#L209-L212

.. need to depend on GetProductVersions.

With this, it fails to find Emscripten manifest for that SdkBandVersion (8.0.100-dev or 8.0.100-ci):

error NU1101: Unable to find package Microsoft.NET.Workload.Emscripten.net7.Manifest-8.0.100-dev.

What is the intended behavior here w.r.t the sdk band used for any dependency manifests?

[steveisok]

https://github.com/steveisok/runtime/blob/ef16a86d343e15c6ac67c5bb3eef47ff9fc1db68/eng/testing/tests.wasm.targets#L337-L338 and https://github.com/steveisok/runtime/blob/ef16a86d343e15c6ac67c5bb3eef47ff9fc1db68/eng/testing/workloads-testing.targets#L209-L212

.. need to depend on GetProductVersions.

With this, it fails to find Emscripten manifest for that SdkBandVersion (8.0.100-dev or 8.0.100-ci):

error NU1101: Unable to find package Microsoft.NET.Workload.Emscripten.net7.Manifest-8.0.100-dev.

What is the intended behavior here w.r.t the sdk band used for any dependency manifests?

I'll try removing the target and see if we get what we expect. I was trying to match what the installer subset was doing.