Publish signed release copies for payload commit d7d20d9

[AmirMS (AmelBawa-msft)]

Summary

Publish signed launcher copies that reference payload commit d7d20d9, matching the source launcher update.

[ranm-msft]

Approving.

This diff is 4 changed files and ~1000 changed lines, but almost all of it is Authenticode signature blocks. Filtering comment lines out leaves exactly 8 semantic lines: the same $payloadRef bump repeated four times, in Workloads/winui/setup.ps1, windows-dev-config/setup-full.ps1, windows-dev-config/setup-standard.ps1 and windows-dev-config/uninstall.ps1.

I verified the new pin rather than taking it on trust:

• d7d20d9077d2801acdd27c8387c481136f100317 resolves to Signed dev config files (#142).
• windows-dev-config/bootstrap.ps1 exists at that ref (37,801 bytes).
• Comparing main...d7d20d9 reports behind_by: 11, ahead_by: 0 - the ref is an ancestor of main, so the pin cannot dangle later.

All four call sites moved together, so there is no split-brain between the setup and uninstall paths. No asks.

[ranm-msft]

Recording the disposition explicitly: approve. (My previous comment has the detail; the verification of the new $payloadRef is in there.)