chore(ci): add breaking change guideline to PR title check (OpenListTeam#2087)

* feat(ci): add PR title validation for breaking changes

Updated regex to allow '!' for breaking changes in PR titles.

Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>

* chore(pr): Update PR template

Add bilingual instructions for PR title formatting.

Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>

---------

Signed-off-by: MadDogOwner <xiaoran@xrgzs.top>

Author: xrgzs

.github/PULL_REQUEST_TEMPLATE.md

@@ -2,11 +2,13 @@
   Provide a general summary of your changes in the Title above.
   The PR title must start with `feat(): `, `docs(): `, `fix(): `, `style(): `, or `refactor(): `, `chore(): `. For example: `feat(component): add new feature`.
   If it spans multiple components, use the main component as the prefix and enumerate in the title, describe in the body.
+  For breaking changes, add `!` after the type, e.g., `feat(component)!: breaking change`.
 -->
 <!--
   在上方标题中提供您更改的总体摘要。
   PR 标题需以 `feat(): `, `docs(): `, `fix(): `, `style(): `, `refactor(): `, `chore(): ` 其中之一开头，例如：`feat(component): 新增功能`。
   如果跨多个组件，请使用主要组件作为前缀，并在标题中枚举、描述中说明。
+  如果是破坏性变更，请在类型后添加 `!`，例如 `feat(component)!: 破坏性变更`。
 -->
 
 ## Description / 描述

.github/workflows/issue_pr_comment.yml

@@ -47,12 +47,14 @@ jobs:
         with:
           script: |
             const title = context.payload.pull_request.title || "";
-            const ok = /^(feat|docs|fix|style|refactor|chore)\(.+?\): /i.test(title);
+            const ok = /^(feat|docs|fix|style|refactor|chore)\(.+?\)!?: /i.test(title);
             if (!ok) {
               let comment = "⚠️ PR 标题需以 `feat(): `, `docs(): `, `fix(): `, `style(): `, `refactor(): `, `chore(): ` 其中之一开头，例如：`feat(component): 新增功能`。\n";
               comment += "⚠️ The PR title must start with `feat(): `, `docs(): `, `fix(): `, `style(): `, or `refactor(): `, `chore(): `. For example: `feat(component): add new feature`.\n\n";
               comment += "如果跨多个组件，请使用主要组件作为前缀，并在标题中枚举、描述中说明。\n";
               comment += "If it spans multiple components, use the main component as the prefix and enumerate in the title, describe in the body.\n\n";
+              comment += "如果是破坏性变更，请在类型后添加 `!`，例如 `feat(component)!: 破坏性变更`。\n";
+              comment += "For breaking changes, add `!` after the type, e.g., `feat(component)!: breaking change`.\n\n";
               await github.rest.issues.createComment({
                 ...context.repo,
                 issue_number: context.issue.number,