feat: v1.8.0 — mutation verbs honour --json / --jq / --template

[trngthnh369]

Follow-up to the review finding on #3, done properly across all mutation verbs
instead of just archive.

The bug

--json silently did nothing on every state-changing command. They wrote a
status line straight to stdout and never went through printData:

$ n8nctl workflow archive 58 --json | jq .id
parse error: Invalid numeric literal at line 1, column 2

No error, no signal — a script just gets ✓ archived workflow 58 "wf" where it
expected JSON. 19 commands now route their result through a new printMutation
helper: workflow activate/deactivate/archive/unarchive/delete/refresh/tag/
transfer, tag create/update/delete, variable set/delete, execution delete,
credential delete/transfer, user delete/role, project create/update/delete/
add-user/remove-user. --dry-run previews are machine-readable too, flagged
"dryRun": true.

Opt-in on purpose — NOT a breaking change

printData's contract §2 says non-TTY is always JSON. Applying that here would
switch piped output to JSON for every existing caller, silently breaking any
script that greps the status line. So printMutation deviates deliberately:

	stdout	stderr
no output flag (TTY or piped)	status line — unchanged	—
--json / --jq / --template	machine-readable data	status line

n8nctl workflow activate 58 | cat          # ✓ activated workflow 58 "wf"   <- unchanged
n8nctl workflow activate 58 --json         # {"id":"58","name":"wf","active":true}
n8nctl workflow archive 58 --jq '.id'      # "58"
n8nctl workflow delete 58 --dry-run --json # {"id":"58",...,"dryRun":true}

Full contract-§2 alignment stays available as a deliberate major-version
decision; it's documented in the helper rather than smuggled in here.

printMutation takes a PrintContext, not a Factory — lib/output.ts must not
depend on factory.ts, which would close an import cycle of exactly the kind that
caused the completion flake fixed in #2.

Verified

• 511 tests (+9), coverage gate green, lint/build/audit clean.
• The 502 pre-existing tests passed unchanged — that's the empirical evidence
  for the non-breaking claim, since the default path is untouched.
• Live through the built CLI: no flag + pipe still emits text; --json pipes
  parseable JSON; --jq filters a field; the status line lands on stderr.

Not tagged — v1.8.0 is bumped in package.json + CHANGELOG.md; tagging
(which triggers the npm release) is left for you.

🤖 Generated with Claude Code