docs(channel-deployment): add missing EN table anchors + Smart Agent extra permissions step

[Eriche985]

What

1. EN page: first four channels in the Supported Channels table had no anchor links (ZH already had them), so clicking them did nothing.

• Added explicit anchor ids to the four option headings, matching the ZH ids: {#telegram} {#lark-feishu} {#wecom} {#dingtalk}
• Linked the Telegram / Lark (Feishu) / WeCom / DingTalk table rows to those anchors

2. Smart Agent Quick Deploy (方案1): added a required-permissions step (Feishu + Lark sections, EN + ZH — 4 places).

The one-click Smart Agent setup only grants basic messaging scopes. In practice the bot then can't read group messages or resolve real user names. New Step 5: Add Required Permissions for Group Chats instructs users to manually enable:

Scope	Purpose
im:message.group_msg	receive group messages / respond to @mentions
im:chat:readonly	read group info & member lists
contact:user.base:readonly	resolve user IDs to real names
contact:user.employee_id:readonly	match users by employee ID

Also covers: set data permission scope to All, and republish the app version if the tenant requires approval (403 hint). The old Step 5 (search bot & chat) is renumbered to Step 6.

Reference: internal permission config guide (luna, 2026-07-08, zylos-lark v0.3.5+).

🤖 Generated with Claude Code

[tyler-0xffff]

LGTM ✅ Reviewed by zylos-tyler.

1. EN table anchors — verified the four new links (#telegram / #lark-feishu / #wecom / #dingtalk) each have a matching {#id} on the corresponding Option heading. This is the same explicit-anchor mechanism every existing table link (WhatsApp/Discord/Slack…) already uses, so it's consistent and will work.

2. Extra-permissions step — added to all 4 required places (EN+ZH × Feishu+Lark 方案1). Scopes match the reference. Step 5→6 renumbering is clean in every section, no collisions or dangling numbers. The 'If missing' symptom column + 403/republish hint are good touches.

Approving.