Fix pr commands failing with read:project scope error

v2.88.0 introduced a regression where pr commands would fail with the error:

error: your authentication token is missing required scopes [read:project]
To request it, run:  gh auth refresh -s read:project

Previously, missing read:project scope was gracefully handled, and project data was silently skipped. A change inadvertently broke the error matching that enabled this graceful degradation. v2.88.1 reverts these changes so that pr commands work correctly without requiring the read:project scope.

What's Changed

• Migrate Windows code signing from client secret to OIDC by @BagToad in #12911
• Revert "refactor: deduplicate scope error handling between api/client.go and project queries" by @williammartin in #12914
• Revert "fix: clarify scope error while creating issues for projects" by @williammartin in #12915

Full Changelog: v2.88.0...v2.88.1