feat(plugin): support selective batch updates

[xxynet]

Closes #10559.

The installed-plugin update action currently updates every plugin with a detected new version. Users cannot skip a plugin while updating others. This change lists available updates with checkboxes, selects all by default, and submits only the checked plugins. For example, with three updates available, unchecking one sends only the other two plugin names to the existing batch update API.

Modifications / 改动点

• Add a scrollable list of localized plugin names and checkboxes to the existing confirmation dialog. Reset to all selected each time the dialog opens, show the selected count, and disable confirmation when no plugins are selected.

• Filter batch update targets by the selection and current update availability before calling pluginApi.updateMany. The affected flow is the installed-plugin confirmation dialog, its composable, and the existing batch update API.

• Rename Update All → Batch Update Plugins and update the confirmation and success messages in all four locales.

• Update the Chinese and English plugin guides and WebUI entry mappings, and record the rename in the unreleased changelog. These documentation changes accompany the same feature to satisfy the repository's WebUI documentation checklist.

• This is NOT a breaking change. / 这不是一个破坏性变更。

Screenshots or Test Results / 运行截图或测试结果

Verification Steps

1. Open Extensions → Installed → Batch Update Plugins with three available updates and one plugin already at its latest version. Verify that only the three available updates are listed and initially checked.
2. Uncheck every plugin: the count becomes zero and confirmation is disabled. Cancel and reopen: all available updates are selected again.
3. Select only one plugin and confirm using a mocked API. Verify that the request contains only {"names":["preview_weather"],"proxy":""} and that the success message refers to selected plugins.
4. Check the renamed entry and revised confirmation text in the browser, and review the Chinese and English documentation against the workflow.

Check Results

• cd dashboard && pnpm exec vue-tsc --noEmit — passed.
• cd dashboard && pnpm build — passed.
• cd dashboard && pnpm i18n:check — passed; all four locales expose 4,130 matching leaf keys.
• Updated locale JSON and {count} placeholders — verified.
• ruff format . — 516 files unchanged; ruff check . — passed.
• cd docs && pnpm run docs:build — passed.
• git diff --check — passed.

Browser verification used sample plugins and a mocked update endpoint; real plugin downloads/reloads and backend tests were not run. The PR changes the frontend selection and documentation without changing API schemas, backend update behavior, or dependencies.

---

Checklist / 检查清单

• 😊 If there are new features added in the PR, I have discussed it with the authors through issues/emails, etc.
  / 如果 PR 中有新加入的功能，已经通过 Issue / 邮件等方式和作者讨论过。

• 👀 My changes have been well-tested, and "Verification Steps" and "Screenshots" have been provided above.
  / 我的更改经过了良好的测试，并已在上方提供了“验证步骤”和“运行截图”。

• 📚 I checked the affected WebUI instructions and screenshots in docs/zh and docs/en against the changed navigation, page structure, and labels, and updated them in this PR (or explained why no documentation update is needed). For renamed, moved, or merged entry points, I included an old entry → new entry mapping in the documentation and changelog.
  / 我已对照变化后的 WebUI 入口、页面结构和术语，核对并在本 PR 中更新 docs/zh 和 docs/en 的相关操作说明与截图（或说明无需更新文档的原因）。入口改名、移动或合并时，已在文档和 changelog 中补充 旧入口 → 新入口 对照。

• 🤓 I have ensured that no new dependencies are introduced, OR if new dependencies are introduced, they have been added to the appropriate locations in requirements.txt and pyproject.toml.
  / 我确保没有引入新依赖库，或者引入了新依赖库的同时将其添加到 requirements.txt 和 pyproject.toml 文件相应位置。

• 😮 My changes do not introduce malicious code.
  / 我的更改没有引入恶意代码。

The feature request is tracked in #10559. Verification steps and test results are provided above; screenshots are stored as PR attachments outside Git.

Summary by Sourcery

Enable selective plugin updates from the installed-plugin batch update workflow while documenting the renamed action and revised behavior.

New Features:

• Allow users to select which available plugins to update in the batch update confirmation dialog, with all updates selected by default.

Enhancements:

• Disable batch update confirmation when no plugins are selected and reset selections whenever the dialog opens.
• Rename the installed-plugin action to “Batch Update Plugins” and update related localized messages.

Documentation:

• Update English and Chinese plugin guides and WebUI mappings to document selective batch updates and the renamed entry.
• Record the renamed batch update workflow in the unreleased changelog.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Needs a human reviewer. If the selection is applied incorrectly, a plugin the user meant to skip could still be updated, changing its installed code and potentially its stored state. Reverting this UI change would not restore that plugin version, though the affected updates are bounded and can generally be repaired by updating or reinstalling the plugin.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook