Release QA report flags PRs linked with "Refs #N" as orphans #37941

The release QA report (.github/scripts/release-qa-status) lists a PR as an Orphan PR even when the PR passed the issue-link check that every PR must pass.

The two disagree on what counts as a linked issue:

• The PR gate (.github/workflows/issue_comp_link-issue-to-pr.yml) accepts closing keywords (Fixes #N), non-closing references (Refs #N, Part of #N, Related to #N), a trailing (#N) on the title, and an issue number in the branch name.
• The release report only reads GitHub's closingIssuesReferences, which covers closing keywords and the Development panel and nothing else.

So a PR that links its issue with Refs #N, on purpose so it doesn't close the issue on merge, is reported as an orphan.

Example: #37714 says Refs #37580 and passed the gate, but v26.10.07-01 reported it as unlinked.

Fix: when a PR has no closing link, fall back to the same non-closing forms the gate accepts, in the gate's order.

Acceptance criteria

• A PR whose only link is Refs #N, Part of #N, a (#N) title suffix, or an issue number in its branch name is no longer counted as an orphan. Its QA status is read from that issue's labels.
• PRs with a closing reference are handled exactly as before.
• Re-running the report on v26.10.07-01 shows 0 orphans, with docs: add Team Scout's testing/tooling half of the gap backlog #37714 linked to M4 — Testing & tooling gap backlog #37580.