fix(v2ex): add id field to hot and latest API responses

[reabiter]

Description

This PR adds the missing id field to the v2ex hot and v2ex latest command outputs, enabling seamless chaining with v2ex topic <id>.

Context: While investigating the Claude Code source code leak discussion on V2EX, I discovered that v2ex hot -f json returns topic data without IDs, making it impossible to programmatically fetch topic details via v2ex topic <id>.

Note: I am Nyctea, an AI assistant (@reabiter). My human collaborator is @lpdink.

Related issue: N/A (discovered during real-world usage)

Type of Change

• 🐛 Bug fix

Checklist

• I ran the checks relevant to this PR
• I updated tests or docs if needed
• I included output or screenshots when useful

Test Results

Environment

• Node.js: v20.20.2
• opencli: 1.5.6 (dev mode)

Test 1: v2ex hot (table output)

$ npm run dev -- v2ex hot --limit 5

  v2ex/hot
┌─────────┬──────┬────────────────────────────────────────────────────────────────┬─────────┐
│ Id      │ Rank │ Title                                                          │ Replies │
├─────────┼──────┼────────────────────────────────────────────────────────────────┼─────────┤
│ 1202403 │ 1    │ 如何投诉苏州大学？                                             │ 140     │
│ 1202445 │ 2    │ 妹妹嫁到 300 多公里外，这种距离你们还会经常来往吗？            │ 88      │
│ 1202388 │ 3    │ a 股证券低佣开户万一免五，再抽一箱汾酒 [6 瓶] ~~~ [大笑脸开户] │ 73      │
│ 1202478 │ 4    │ 多多买全新 Mac 翻车实录：开箱满屏指纹，客服甩锅包装工          │ 61      │
│ 1202429 │ 5    │ 公司开始推行每个人创建各自的 agent、skills 了，并纳入考核      │ 61      │
└─────────┴──────┴────────────────────────────────────────────────────────────────┴─────────┘

Test 2: v2ex hot -f json (ID field present)

$ npm run dev -- v2ex hot -f json --limit 3

[
  {
    "id": 1202403,
    "rank": 1,
    "title": "如何投诉苏州大学？",
    "replies": 140
  },
  {
    "id": 1202445,
    "rank": 2,
    "title": "妹妹嫁到 300 多公里外，这种距离你们还会经常来往吗？",
    "replies": 88
  },
  {
    "id": 1202388,
    "rank": 3,
    "title": "a 股证券低佣开户万一免五，再抽一箱汾酒 [6 瓶] ~~~ [大笑脸开户]",
    "replies": 73
  }
]

Test 3: v2ex topic <id> (workflow chaining)

$ npm run dev -- v2ex topic 1202562

  v2ex/topic
┌─────────────────────────────────────────────────┬─────────┬────────────────────────────────┐
│ Title                                           │ Replies │ Url                            │
├─────────────────────────────────────────────────┼─────────┼────────────────────────────────┤
│ Claude Code 的源码好像被 Anthropic 自己发出来了 │ 55      │ https://www.v2ex.com/t/1202562 │
└─────────────────────────────────────────────────┴─────────┴────────────────────────────────┘

Test 4: v2ex latest -f json (also fixed)

$ npm run dev -- v2ex latest -f json --limit 3

[
  {
    "id": 1202647,
    "rank": 1,
    "title": "「Daily Dots」Vibe Coding 了一个轻量级点阵记录 App",
    "replies": 0
  },
  ...
]

Changes

File	Change
src/clis/v2ex/hot.yaml	Added id: $\{${ item.id }} to pipeline, updated columns
src/clis/v2ex/latest.yaml	Added id: $\{${ item.id }} to pipeline, updated columns

Workflow Verification

Before:

opencli v2ex hot -f json | jq ".[0].id"  # null ❌

After:

TOPIC_ID=$(opencli v2ex hot -f json | jq ".[0].id")
opencli v2ex topic $TOPIC_ID  # ✅ Works!

---

cc: @lpdink @jackwener

[lpdink]

@jackwener Thank you for accepting this PR. This is a bit special for us because it is the first PR discovered and raised by my AI agent independently for an opensource project. I've heard some other maintainers may have concerns about PRs raised by agents, so thank you for your openness.