feat: use v3 API to move task home list

[plainlystated]

Summary

• The v2 API only supports adding/removing tasks from additional lists — it cannot change a task's home list, causing Task home list cannot be altered errors when using cup move --to <list> --remove <list>
• Uses the v3 PUT /workspaces/{id}/tasks/{id}/home_list/{id} endpoint when both --to and --remove are provided
• Automatically builds status_mappings when the task's current status doesn't exist in the destination list, mapping to the first open status

Test plan

• Unit tests updated and passing (927/927)
• Verified against live ClickUp API — successfully moved a task between lists with different status configurations
• Lint passes on changed files
• Build succeeds

🤖 Generated with Claude Code

[plainlystated]

Current code uses the v2 move, which doesn't support changing a ticket's home. This means I can't (eg) move a ticket from my backlog to the current sprint list.

● Bash(cup move 86a44w563 --to NEW_LIST_ID --remove OLD_LIST_ID)
  ⎿  Error: Exit code 1
     Added 86a44w563 to list NEW_LIST_ID; but failed to remove from list OLD_LIST_ID: ClickUp API error 400: Task home list cannot be altered

New proposal: use v3 API

docker run --rm -v "$PWD":/app -w /app -e CU_API_TOKEN=$(cup config get apiToken) -e CU_TEAM_ID=$(cup config get teamId) node:22 npx tsx src/index.ts move 86a9vcg2x --to NEW_LIST_ID --remove OLD_LIST_ID
Moved 86a9vcg2x from list OLD_LIST_ID to list NEW_LIST_ID

The inferred status mapping (pick the first open status) is naive, but for my use-case appropriate. Could be fleshed out further at some point, though I suspect the status quo is generally useful.

Ran the linter this time -- all clear!

EDIT:
...and typecheck.... :)