Suggestion: Document job's `permissions: copilot-requests: write` as an auth mechanism

Currently the readme advises using a PAT to allow Copilot to be used: https://github.com/github/copilot-release-notes#authentication

However, for most use cases when using workflows it's a better practice to have the workflow run under the repo's budget rather than as an invidiual user (which would use their AI credits and would break if they left / lost their copilot license / etc).

Is it worth updating the root README.md with a note on using the job's permissions to enable `copilot-requests: write` for this, per guidance: https://docs.github.com/en/copilot/how-tos/copilot-cli/use-copilot-cli-in-actions#recommended-approach-github-agentic-workflows

Comece pelas orientações de autenticação no README.md raiz e compare-as com a documentação do GitHub vinculada sobre a abordagem recomendada. Documente como um job de workflow pode usar `permissions: copilot-requests: write` em vez de um PAT e confirme que o README explica claramente quando essa autenticação baseada em orçamento é preferível.

Escrita pelo modelo de indexação a partir do texto da issue.