Add regression test for required scopes parsing - #12803

Thanks for your pull request! Unfortunately, it doesn't meet the minimum requirements for review:

• None of the referenced issues have the help-wanted label

Please update your PR to address the above. Requirements:

1. Include a detailed description of what this PR does
2. Link to an issue with the help-wanted label (use Fixes #123 or Closes #123 if it resolves the issue)

This PR will be automatically closed in 7 days if these requirements are not met.

@BagToad Quick question: the review-bot still reports that none of the referenced issues have the help wanted label. Issue #12585 currently shows help wanted on my side (and that's what this regression test targets). Could you please add/confirm the exact label the bot expects (e.g. help-wanted vs help wanted) on #12585 so this PR meets the review requirements?

Thanks for the contribution! However, this test already passes on trunk — the scope parsing for this message format was never broken. The actual bug in #12585 is that the parsed scopes aren't surfaced as a friendly gh auth refresh suggestion in the gh issue create code path, which is addressed by #12596.

Merging this would also incorrectly close #12585 via the "Fixes" keyword without actually fixing the UX issue.

@BagToad Quick question: the review-bot still reports that none of the referenced issues have the help wanted label. Issue #12585 currently shows help wanted on my side (and that's what this regression test targets). Could you please add/confirm the exact label the bot expects (e.g. help-wanted vs help wanted) on #12585 so this PR meets the review requirements?

BTW I fixed this in desktop/gh-cli-and-desktop-shared-workflows#7 - thank you for mentioning this!