Make Post Release resilient to WinGet token auth failures

[Copilot]

Post Release started failing at the Publish to WinGet job because winget-releaser aborted with GitHub token is invalid when using WINGET_TOKEN. This change keeps the release workflow actionable by surfacing the WinGet failure as an explicit warning instead of failing the whole workflow run.

• Root cause observed

  • winget-releaser fails during komac update --submit with an invalid token error, causing the Post Release workflow to fail.

• Workflow behavior change

  • Added an explicit step id for the WinGet publish step.
  • Marked the WinGet publish step as non-blocking (continue-on-error: true).
  • Added a conditional warning step that runs only when WinGet publish fails and points maintainers to token scope/type expectations.

• Resulting release semantics

  • Release follow-up automation no longer hard-fails on WinGet PAT auth errors.
  • Failure is still visible and actionable via a targeted warning.

- id: publish-winget
  uses: vedantmgoyal2009/winget-releaser@v2
  continue-on-error: true
  with:
    identifier: dail8859.NotepadNext
    token: ${{ secrets.WINGET_TOKEN }}

- name: Report WinGet publish failure
  if: steps.publish-winget.outcome == 'failure'
  run: |
    echo "::warning::WinGet publish failed. The WINGET_TOKEN is likely invalid or missing required permissions. Configure a classic PAT with public_repo scope."