chore(ci): verify changeset-feedback action compatibility for 0.7.8 bump

[Copilot]

This PR validates whether upgrading backstage/actions/changeset-feedback from v0.6.17 to v0.7.8 changes behavior for our only requirement: posting/updating changeset feedback comments on PRs.
The review confirms no functional drift in the action implementation used by our workflow.

• Scope of review

  • Compared changeset-feedback across both tags (v0.6.17 and v0.7.8) at source level.
  • Focused on files that define runtime behavior and contract:
    • action.yaml
    • entry.js
    • index.ts
    • generateFeedback.ts
    • postFeedback.ts

• Findings

  • The action contract (inputs/outputs) is unchanged for our usage.
  • The execution path that computes and posts PR changeset feedback is unchanged.
  • No migration to an alternative action or in-repo fork is required at this time.

• Resulting PR impact

  • Keeps the existing version bump as-is.
  • Adds compatibility confirmation in review context, so the dependency update remains low-risk for this workflow.

- name: Generate feedback
  uses: backstage/actions/changeset-feedback@2cd6978b476cbdc39fec48346f8b6ca13199dd6a # v0.7.8
  with:
    diff-ref: origin/main
    issue-number: ${{ github.event.pull_request.number }}
    bot-username: wasmcloud-automation-app[bot]
    app-id: ${{ secrets.BOT_APP_ID }}
    private-key: ${{ secrets.BOT_APP_PRIVATE_KEY }}
    installation-id: ${{ secrets.BOT_APP_INSTALLATION_ID }}

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.