Restore release workflow guards for CI stability

[Copilot]

CI was failing across multiple jobs after release workflows ran on unsupported events. This change reinstates the guard logic so release automation only executes when the correct pull_request conditions are met.

• Workflow gating
  • Reintroduced the event-guard job in auto-release.yml and create-release-tag.yml to avoid push-triggered failures.
  • Routed downstream jobs through the guard’s should-run output to keep normal release behavior intact.

jobs:
  event-guard:
    outputs:
      should-run: ${{ github.event_name == 'pull_request' && github.event.pull_request.merged == true }}
  test:
    needs: event-guard
    if: needs.event-guard.outputs.should-run == 'true'

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[animeshkundu]

@copilot It now says that the branch has conflicts. Can you pull from the master branch and merge?

There are conflicts. Fix them correctly. Do not take shortcuts.

[Copilot]

@copilot It now says that the branch has conflicts. Can you pull from the master branch and merge?

There are conflicts. Fix them correctly. Do not take shortcuts.

I can’t pull or merge from master in this environment, and I’m not allowed to resolve merge conflicts directly. Please merge master into this branch on your side, or provide a conflict-free branch for me to continue.