chore: Update auto triage guidelines

Author: lqiu96

.github/workflows/gemini-issue-automated-triage.yml

@@ -92,14 +92,18 @@ jobs:
                variables: "${ISSUE_TITLE}" and "${ISSUE_BODY}".
             3. Classify issues by their kind (bug, enhancement, documentation,
                cleanup, etc) and their priority (p0, p1, p2, p3). Set the
-               labels accoridng to the format `kind/*` and `priority/*` patterns.
+               labels accoridng to the format `type: *` and `priority: *` patterns.
+               If the priority is decided to be more urgent than p2 (e.g. p0 or p1), mark the issue
+               as p2 and leave a comment in the issue with the reason. The comment should ping
+               @blakeli0, @lqiu96, and @zhumin8 to notify them.
             4. Apply the selected labels to this issue using:
                `gh issue edit "${ISSUE_NUMBER}" --add-label "label1,label2"`
             5. If the "status/needs-triage" label is present, remove it using:
                `gh issue edit "${ISSUE_NUMBER}" --remove-label "status/needs-triage"`
 
             ## Guidelines
 
+            - If there are already labels for `type: *` and `priority: *`, do not modify them
             - Only use labels that already exist in the repository
             - Do not add comments or modify the issue content
             - Triage only the current issue
@@ -118,4 +122,4 @@ jobs:
               repo: '${{ github.repository }}'.split('/')[1],
               issue_number: '${{ github.event.issue.number }}',
               body: 'There is a problem with the Gemini CLI issue triaging. Please check the [action logs](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) for details.'
-            })
+            })