"Copilot Requests" permission for fine-grained tokens should be visible for org-owned tokens

[RyanHecht]

Describe the feature or problem you'd like to solve

The "Copilot Requests" Permission does not display when creating a token owned by an organization

Proposed solution

Organizations do not want individual user PAT's being used to authenticate automations in corporate environments. This will unblock automation use cases for organizations

Example prompts or workflows

Additional context

No response

[arqex]

My use case for this:

• I'm trying to run copilot cli in a sandbox, where gh command is configured
• Gh is authenticated with the organization token, for managing pull requests
• Copilot cli get authenticated by using gh token, that has no copilot request permission
• Copilot can't find any model because the lack of that permission, so can't be used

I have to choose, either I can use gh for accessing the repo, or I can use copilot CLI but I can't use both with one token in the same sandbox.

Please enable "copilot requests" permission for organization owned tokens, or enable a different token authentication for github cli.