fix: accept v1.0.2 WinGet installer URL

[HelloThisWorld]

Summary

• Fix the post-release WinGet CI failure for the public v1.0.2 installer.
• Add a release Smoke assertion so a stale installer URL validation rule is caught before future publication.

Related issues

None.

Detailed changes

• Update generate-winget-manifests.ps1 to accept only the immutable public v1.0.2 MSIX URL instead of the stale v1.0.1 URL.
• Extend test-release-workflow.ps1 to verify that the generator requires the current release URL and rejects a stale hard-coded v1.0.1 path.
• Do not modify, replace, or rebuild any v1.0.2 Release asset or move the existing tag.

Validation performed

• Reproduced the failure in WinGet workflow run 29686787885: the generator rejected the valid v1.0.2 URL because its ValidatePattern still required v1.0.1.
• Windows PowerShell 5.1 on Windows 11 x64:
  • Executed generate-winget-manifests.ps1 with the public v1.0.2 installer URL and a test SHA-256.
  • Result: all three WinGet manifest files generated successfully.
• powershell.exe -NoLogo -NoProfile -ExecutionPolicy Bypass -File scripts/winterm/test.ps1 -Suite Smoke
  • Result: passed.
• git diff --check
  • Result: passed.

Checklist

• The change is focused and does not include unrelated formatting.
• Tests were added or updated where appropriate.
• All tests claimed above actually ran and passed.
• User-facing behavior and limitations are documented in this repository.
• Version or schema changes include compatibility and migration notes.
• Package identity, winterm.exe, and Microsoft Terminal coexistence remain isolated.
• No command text, terminal output, clipboard content, credentials, or private paths are logged.
• New source and script files contain the appropriate MIT license header.
• I did not include generated build output, secrets, certificates, or local absolute paths.