Adjustment of Gemini Workflow to use GEMINI_PAT

[omatheusmesmo]

This pull request updates several GitHub Actions workflow files to improve authentication and clarify label handling. The main focus is on prioritizing the use of the GEMINI_PAT secret for authentication across all Gemini-related workflows and making the labeling logic in the triage workflow more accurate and descriptive.

Authentication improvements:

• All Gemini-related workflow steps now use the GEMINI_PAT secret as the primary authentication token, falling back to other tokens only if it is not set. This change increases security and consistency when running Gemini automation. [1] [2] [3] [4] [5]

Labeling logic improvements:

• In the gemini-triage.yml workflow, the script now uses addLabels instead of setLabels to append labels to issues or pull requests, and updates log messages to reflect this change, making the labeling process more accurate and the logs clearer.

[github-actions]

🤖 Hi @omatheusmesmo, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[github-actions]

📋 Review Summary

This pull request introduces a consistent change across several GitHub Actions workflows to prioritize secrets.GEMINI_PAT as the GITHUB_TOKEN, providing an additional fallback mechanism. The changes are straightforward and appear to be a sensible improvement for token management within the CI/CD environment.

🔍 General Feedback

• The changes are consistently applied across all modified workflow files.
• The addition of secrets.GEMINI_PAT provides more flexibility in token management.