[#57]

Add the ability to move issues between projects using Jira Cloud's bulk move API.

Summary

• Add jtk issues move <issue-key>... --to-project <project> command
• Add jtk issues move-status <task-id> to check async operation status
• Uses Jira Cloud bulk move API (not available on Server/Data Center)

Usage

# Move a single issue to another project
jtk issues move PROJ-123 --to-project NEWPROJ

# Move to specific issue type
jtk issues move PROJ-123 --to-project NEWPROJ --to-type Task

# Move multiple issues
jtk issues move PROJ-123 PROJ-124 PROJ-125 --to-project NEWPROJ

# Move without waiting for completion
jtk issues move PROJ-123 --to-project NEWPROJ --no-wait

# Check move task status
jtk issues move-status abc123

Features

• Automatically infers target issue type from source (or specify with --to-type)
• Async operation with built-in polling (--wait is default, use --no-wait for fire-and-forget)
• Notification control via --notify flag
• Reports successes and failures when operation completes
• Maximum 1000 issues per request (Jira API limit)

Limitations (Jira API constraints)

• Jira Cloud only - not available on Server/Data Center
• Subtasks must be moved with their parent or separately
• Some field values may need manual remapping

Test plan

• All existing tests pass
• Lint passes
• Command help works correctly
• Manual testing with real Jira Cloud instance

Closes #57