fix: refresh platform commands after command changes

[casama233]

Follow-up to #4485.

#4485 correctly made Telegram and Discord skip disabled handlers when platform commands are collected, but runtime changes from Dashboard → Plugins → Manage Behaviors do not currently trigger a platform command re-sync. As a result, disabling or renaming commands updates AstrBot's runtime state while already-registered native commands can remain stale on the platform. This is especially problematic near platform command-count limits because disabling commands does not promptly free those native command slots.

Modifications / 改动点

• Add a default no-op Platform.refresh_registered_commands() hook so adapters that expose native commands can opt into runtime refresh without platform-specific conditionals in the dashboard service.
• Refresh platform-native command registrations after a command is successfully enabled/disabled or renamed.
• Discord:
  • replace only AstrBot-managed application commands before syncing;
  • serialize command refreshes with a lock;
  • roll back the managed local registry if synchronization fails;
  • pass the configured debug guild through check_guilds so stale guild commands can also be removed when the desired command set becomes empty;
  • preserve the existing daily application-command quota handling (30034).
• Telegram:
  • refresh native commands for a running application after command-management changes;
  • delete stale platform commands when the desired command set becomes empty;
  • update the command hash only after the platform update succeeds so failed updates remain retryable.
• Add regression coverage for command toggle/rename refresh, Discord disable/removal and rollback behavior, debug-guild empty-set synchronization, and Telegram empty-command cleanup/runtime refresh.

This is intentionally limited to the adapters that currently expose AstrBot-managed native command registration (Discord and Telegram). Other adapters inherit the no-op hook.

This is not a duplicate of #4485:

• fix:exclude disabled commands from platform command registration #4485: disabled handlers are excluded on the next collection.

• This PR: runtime command-management changes trigger that collection/sync for already-running adapters.

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

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

Verification on the final PR commit:

• Code Format Check ✅
• Unit Tests ✅
• Smoke Test ✅
• AstrBot Dashboard CI ✅
• CodeQL ✅

The regression tests added in this PR cover:

• command toggle and rename refreshing platform commands;
• Discord removing a command after its handler is disabled;
• Discord debug-guild empty-set synchronization;
• Discord local-registry rollback on synchronization failure;
• Telegram deleting stale commands when the desired set becomes empty;
• Telegram refresh only running for a started, command-registration-enabled adapter.

---

Checklist / 检查清单

• 😊 No new feature is introduced; this PR is a bug fix and a follow-up to fix:exclude disabled commands from platform command registration #4485.
• 👀 My changes have been well-tested, and verification results are provided above.
• 🤓 No new dependencies are introduced.
• 😮 My changes do not introduce malicious code.

[sourcery-ai]

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

---

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

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}