Fix merge conflict detection in pr-review-needed workflow

[Copilot]

Description

The workflow was incorrectly detecting merge conflicts because mergeable_state is not available in the pulls.list API response—it requires fetching individual PR details via pulls.get. Additionally, the initial implementation only checked for mergeable_state === 'dirty', which missed edge cases where PRs have merge conflicts but GitHub doesn't explicitly set the state to 'dirty'.

Changes:

• Fetch full PR details individually to access mergeable_state and mergeable fields
• Implement comprehensive conflict detection logic:
  • Primary check: mergeable_state === 'dirty' (definitive conflicts)
  • Secondary check: mergeable === false AND state is not blocked, behind, unstable, unknown, or clean (catches edge cases)
• Add detailed comments explaining all possible mergeable_state values and their meanings
• Exclude non-conflict blocking states (blocked by checks/reviews, behind base branch, unstable checks, etc.)

This ensures all PRs with actual merge conflicts are correctly identified and marked with the ❌ emoji in the tracking issue, including edge cases that were previously missed.

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

---

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

[radical]

@copilot we are still missing some cases like #11363 - the report did not have X for it.

[Copilot]

@copilot we are still missing some cases like #11363 - the report did not have X for it.

Enhanced the conflict detection logic in commit 34f00bd. The workflow now checks both mergeable_state === 'dirty' and the broader case of mergeable === false (excluding states like blocked, behind, unstable, unknown, clean which indicate non-conflict blocking reasons). This should catch edge cases where GitHub reports a PR as unmergeable due to conflicts but doesn't explicitly set the state to 'dirty'.