ci: grant pull-requests:read so lint-pr-title workflow starts

[kinyoklion]

Summary

Adds permissions: pull-requests: read at the workflow level in .github/workflows/lint-pr-title.yml.

The reusable workflow at launchdarkly/gh-actions/.github/workflows/lint-pr-title.yml@main was updated (launchdarkly/gh-actions#86) to declare permissions: pull-requests: read at the job level. A reusable workflow can only request a subset of the permissions the caller grants, so without an explicit permissions block in the caller, every run hits startup_failure. Same fix as launchdarkly/sdk-meta#429.

Review & Testing Checklist for Human

• Verify the Lint PR title check on this PR exits success rather than startup_failure

Notes

No product code is changed — workflow-only permissions fix being applied across SDK repos that use the reusable lint-pr-title workflow.

Link to Devin session: https://app.devin.ai/sessions/c7b96da5c9074500aa684bc9a9ba1c31
Requested by: @kinyoklion

---

Note

Low Risk
Low risk: only adjusts GitHub Actions workflow permissions and does not touch product code. The main impact is whether the PR-title lint job can start and access PR metadata as intended.

Overview
Updates the Lint PR title GitHub Actions workflow to explicitly grant pull-requests: read permissions at the workflow level.

This aligns caller permissions with the reusable launchdarkly/gh-actions lint workflow so runs don’t fail at startup due to insufficient PR access.

^{Reviewed by Cursor Bugbot for commit 769ec7c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring