feat: refactor User/Bot architecture and implement multi-channel gateway

Major changes:
1. Core Architecture: Decoupled Bots from Users. Bots now have independent lifecycles, member management (bot_members), and dedicated configurations.
2. Channel Gateway:
   - Implemented a unified Channel Manager supporting Feishu, Telegram, and Local (Web/CLI) adapters.
   - Added message processing pipeline to normalize interactions across different platforms.
   - Introduced a Contact system for identity binding and guest access policies.
3. Database & Tooling:
   - Consolidated all migrations into 0001_init with updated schema for bots, channels, and contacts.
   - Optimized sqlc.yaml to automatically track the migrations directory.
4. Agent Enhancements:
   - Introduced ToolContext to provide Agents with platform-aware execution capabilities (e.g., messaging, contact lookups).
   - Added tool logging and fallback mechanisms for toolChoice execution.
5. UI & Docs: Updated frontend stores, UI components, and Swagger documentation to align with the new Bot-centric model.

internal/schedule/trigger.go

@@ -0,0 +1,18 @@
+package schedule
+
+import "context"
+
+// TriggerPayload 描述触发定时任务时传递给聊天侧的参数。
+type TriggerPayload struct {
+	ID          string
+	Name        string
+	Description string
+	Pattern     string
+	MaxCalls    *int
+	Command     string
+}
+
+// Triggerer 负责触发与聊天相关的调度执行。
+type Triggerer interface {
+	TriggerSchedule(ctx context.Context, botID string, payload TriggerPayload, token string) error
+}