Add workload install --from-rollback-file documentation

[maxkoshevoi]

This page doesn't even specify that workload install (or workload update) has a --from-rollback-file parameter.
I found it it accidentally from comment here.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2bbfaa61-ebac-d118-6dd1-152a53f37a91
• Version Independent ID: 55bbba16-ae98-5abc-cd42-1b677105fd29
• Content: dotnet workload install command - .NET CLI
• Content Source: docs/core/tools/dotnet-workload-install.md
• Product: dotnet-fundamentals
• Technology: dotnet-cli
• GitHub Login: @tdykstra
• Microsoft Alias: tdykstra

[tdykstra]

That option was deliberately hidden and not documented. We plan to generate the rollback file internally and distribute it to users if/when we discover a bug. We’ll also provide instructions for the --from-rollback-file option at that time,

[dotMorten]

That option was deliberately hidden and not documented

That makes no sense. We need this to be able to make reproducible builds.
For example: if you install .net sdk, and then install the maui workload on top, you have no idea what workload version you're getting. The other day Maui deployed RC2.1 which caused a regression from RC2.0, but we never actually updated the .NET 8 SDK from RC2.0. What we really need for reproducible builds is to ensure workloads are locked to a specific version until a new version has been certified.

[tdykstra]

That option was deliberately hidden and not documented

That makes no sense. We need this to be able to make reproducible builds.

cc @baronfel

[tdykstra]

Closing this issue, as the new workload sets feature (available in preview in .NET 9) is intended to resolve the problem that --from-rollback-file was needed for.