ci: open the winget-pkgs update PR when a stable release is published

[lippdev]

What

New winget job in release.yml. After the build job publishes a release from a v* tag, it runs vedantmgoyal9/winget-releaser to open the update PR on microsoft/winget-pkgs for lippdev.ConsoleMode.

• Stable tags only: tags with a - (alpha/beta) are skipped.
• Only the installer is used (ConsoleMode-Setup-x64.exe), not the portable exe.
• The job does nothing until the WINGET_TOKEN secret exists (classic PAT with public_repo, from the account that owns the lippdev/winget-pkgs fork), so merging is safe.

Not verified

CI only builds/tests the app; this workflow runs on tag pushes, so it can't be exercised here. It will first run on the next stable release (after the secret is set). Nothing was built locally (macOS).

🤖 Generated with Claude Code

[pullfrog]

Important

The documented token permissions can make the new release automation fail intermittently.

Reviewed changes This review covers the release workflow's new WinGet submission job and its changelog entries.

• Stable release submission Adds a post-build job that invokes WinGet Releaser for stable tag pushes, when WINGET_TOKEN is configured, and selects the installer asset.
• Changelog entries Announces the automation in both localized changelogs.

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using GPT Luna ｜ 𝕏}

[pullfrog]

The upstream action docs require the PAT's workflow scope when it needs to sync upstream workflow-file changes into the winget-pkgs fork; with only public_repo, that sync can fail intermittently and prevent this release's submission. Please include workflow in the required token permissions or document that the fork must be manually synced when the action reports this failure. Source: https://github.com/vedantmgoyal9/winget-releaser#getting-started-