feat(api): add --verbose, --paginate, --no-auth flags + log resolved URL to apify api

[DaveHanns]

Summary

apify api is a great REST escape hatch, but when an agent (or a human) uses it to
debug, three things are painful: the resolved outbound URL is invisible, walking a
paginated endpoint requires a manual offset loop, and hitting an auth-less resource
(e.g. the actor-templates manifest on raw GitHub) requires reaching for curl
instead of the same command. This PR adds three additive, independent flags —
--verbose, --paginate (+ --paginate-max), and --no-auth — to close those
gaps without changing any existing behavior.

Refs internal findings F31 + EF8.

What changes

src/commands/api.ts only. All flags default to off; omitting them yields
byte-identical behavior to today.

• --verbose / -v — logs -> METHOD URL to stderr before the fetch and
  <- STATUS statusText (content-type) after. Payload still goes to stdout, so
  apify api ... --verbose | jq . keeps working.
• --paginate — for responses shaped like { data: { items, total, offset, limit } } (the Apify pagination envelope), advances offset until total is
  exhausted and emits all collected items as a single JSON array on stdout.
  Errors loudly with a clear message if the response isn't paginated instead of
  silently truncating. --paginate restricted to GET.
• --paginate-max N — cap items collected across pagination.
• --no-auth — skips the Authorization header. Also lets the endpoint
  argument be an absolute https://... URL so the same command can hit
  raw.githubusercontent.com etc. When --no-auth is set we do not require a
  logged-in client (so this works out of the box in fresh environments).

Also adds four apify api --help examples covering the new flags.

Test plan

• apify api users/me --verbose prints the resolved GET https://api.apify.com/v2/users/me line and status line to stderr; payload still lands on stdout.
• apify api acts --paginate walks all pages and emits one JSON array; the array length equals data.total of the first page.
• apify api acts --paginate --paginate-max 5 returns exactly 5 items.
• apify api POST acts --paginate errors out with "can only be used with GET requests".
• apify api users/me --paginate errors out with "expected a { data: { items } } response shape".
• apify api --no-auth https://raw.githubusercontent.com/apify/actor-templates/master/templates/manifest.json fetches the file without an Authorization header, even when not logged in.
• All three flags compose: apify api acts --paginate --verbose --paginate-max 10 prints request/response lines per page and returns 10 items.
• pnpm exec oxlint --type-aware src/commands/api.ts passes.
• pnpm exec tsc --noEmit -p . passes.