fix: WP Performance Metrics CI check fails with GitHub API token scope error

[superdav42]

Summary

The WP Performance Metrics job fails with a GitHub API permission error on PR #470 (run 23554305690).

Error: RequestError [HttpError]: Resource not accessible by integration
URL: https://api.github.com/repos/Ultimate-Multisite/ultimate-multisite/issues/470/comments

The job attempts to post a comment via the GitHub API but the workflow token lacks issues:write permission. All other CI checks pass. This is a workflow permission issue, not a code regression.

Fix: Add issues:write or pull-requests:write permission to the WP Performance Metrics job in the workflow file.

[superdav42]

Dispatching worker.

• Model: sonnet (anthropic/claude-sonnet-4-6)
• Branch: to be created
• Scope: Add issues:write or pull-requests:write permission to the WP Performance Metrics job in the Unit & Integration Tests workflow
• Attempt: 1 of 1
• Direction: The job at line ~end of .github/workflows/unit-integration-tests.yml (or similar) makes a GitHub API call to post a PR comment. Add the required permission to the job-level permissions block.

[superdav42]

Completed via PR #472

What was done:

• Added permissions block to the wp-performance job in .github/workflows/tests.yml
• Granted pull-requests: write so swissspidy/wp-performance-action@v2 can post PR comments
• Granted contents: read (least-privilege, required for actions/checkout)

How it was tested:

• Verified against the original failing run (23554305690): token had only Contents: read, Metadata: read, Packages: read — no PullRequests: write
• Verified against the PR run (23554926105): token now shows PullRequests: write — the Resource not accessible by integration error is gone
• The new failure in the PR run (ECONNREFUSED 127.0.0.1:9400) is a pre-existing WordPress server startup issue unrelated to this fix; the job has continue-on-error: true

Key decisions:

• Added permissions at job level (not workflow level) to keep scope minimal — only wp-performance needs write access
• Used pull-requests: write rather than issues: write since the action posts to the PR, not a standalone issue

Files changed:

• .github/workflows/tests.yml — added permissions: { contents: read, pull-requests: write } to wp-performance job

Blockers encountered: None

Follow-up needs:

• The ECONNREFUSED 127.0.0.1:9400 failure in the performance test (WordPress server not starting) may warrant a separate investigation, but it is pre-existing and non-blocking (continue-on-error: true)