Expose cycles in issue query, mine, and view

[schpetbot]

Adds cycle visibility across issue output and makes cycle updates easy.

Tables (issue query, issue mine)

New compact CYC column, shown only when a listed team has cycles enabled:

• now (green) — the team's active cycle
• +1 / -1 — from the API's isNext/isPrevious flags (these take precedence so display always agrees with --cycle next/previous selection)
• +N / -N — offset from team.activeCycle.number
• #N — absolute fallback when there is no anchor (cooldown or before the first cycle starts)
• - — no cycle

issue view

The Cycle meta part now reads **Cycle:** #7 Sprint 7 (now) / #8 (+1) using the same vocabulary.

JSON

issue query --json / issue view --json now carry cycle { id number name isActive isNext isPrevious isFuture isPast } and team { cyclesEnabled activeCycle { number } } in raw GraphQL shape.

Updating cycles

• issue update <id> --cycle next — also now, previous, and signed offsets (+2, --cycle=-1); relative offsets require an active cycle and error with guidance otherwise
• issue update <id> --clear-cycle — sends an explicit cycleId: null (mirrors --unassign); conflicts with --cycle
• The same vocabulary works for --cycle filters on issue query/issue mine/issue create and cycle view
• Reserved words shadow coincidental cycle names; use the cycle number to reach a cycle literally named "next"

Fixes and hardening

• issue query --search --cycle silently dropped the cycle filter; it now filters
• Cycle lookup paginates past the first 250 cycles
• Using --cycle against a team with cycles disabled now errors with "Cycles are not enabled for team X" instead of a generic not-found