Fix CI release job trigger path and custom token wiring for gh release

[Copilot]

The release workflow was not completing automatically due to an invalid artifact action version and auth wiring that depended on a disallowed secret naming pattern (GITHUB_*). This update aligns the workflow with supported action versions and uses a repository-defined custom secret for release authentication.

• Release job reliability

  • Updated artifact download action to a valid published version.
  • Ensures the release job can fetch cross-platform build artifacts before publishing.

• Release authentication via custom secret

  • Switched CLI auth source from secrets.GITHUB_TOKEN to secrets.GITHUBI through GH_TOKEN.
  • Supports repositories where users cannot create secrets with reserved GITHUB_ prefixes.

• Workflow delta (release step)

  - uses: actions/download-artifact@v4
  
  - name: Upload to GitHub Release
    env:
      GH_TOKEN: ${{ secrets.GITHUBI }}
    run: |
      gh release create "${{ github.ref_name }}" \
        --repo "${{ github.repository }}" \
        --generate-notes \
        release-artifacts/*.AppImage \
        release-artifacts/*.deb \
        release-artifacts/*.exe \
        release-artifacts/*.dmg

[Copilot]

Pull request overview

This PR updates the CI release job to reliably download build artifacts and authenticate gh release create when publishing tag-based releases.

Changes:

• Replace actions/download-artifact@v5 with the published @v4 release.
• Add GH_TOKEN wiring for the gh release create step via a repository secret.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.