Fix props-bot workflow trigger for PR reviews in forked repositories

[Copilot]

The props-bot workflow condition incorrectly used ! github.event.pull_request.head.repo.fork to filter cross-repo PRs. When the repository itself is a fork, same-repo PRs (branch-to-branch) also have head.repo.fork = true, preventing the workflow from running on reviews.

Changes

Changed the fork detection logic to compare repository identities:

# Before
( contains(...) && ! github.event.pull_request.head.repo.fork )

# After  
( contains(...) && github.event.pull_request.head.repo && github.event.pull_request.head.repo.full_name == github.event.pull_request.base.repo.full_name )

This allows same-repo reviews to trigger the workflow while blocking cross-repo PRs and handling null head repos (deleted forks).

Trac ticket:

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

Original prompt

There's a GitHub action that runs to add comments like this to PRs: @WordPress/wordpress-developWordPress/pull/10809

It's supposed to comment to reference the folks who have contributed to a change.

It seems to be missing a PR feedback trigger. In that example, the PR was approved, but the person who approved the PR is not included in the props comment.

Locate the related GitHub action workflow, find its triggers, and correct them to also run on PR reviews.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[sirreal]

@copilot You have misundersood the problem.

The issue is that pull request review events do not trigger the workflow.
There should be no changes to the workflow related to forks or different repos.