feat(cli): split cloud render --resolution into --aspect-ratio + --resolution

[jrusso1020]

What

Aligns the hyperframes cloud render CLI with the v3 API's decomposed resolution shape (companion to https://github.com/heygen-com/experiment-framework/pull/38182). Replaces the flat 6-value --resolution flag with two independent flags:

• --resolution: tier ∈ {1080p, 4k}; default 1080p; 4K is billed at 1.5x by the API.
• --aspect-ratio: ratio ∈ {16:9, 9:16, 1:1}; default 16:9.

Old CLI values (landscape, portrait-4k, etc.) now reject at the flag-parsing layer (parseEnumFlag → Invalid --resolution) so callers see a clean local error instead of a server 422.

Why

Today the CLI exposes the same 6-string flat preset (landscape, landscape-4k, portrait, portrait-4k, square, square-4k) that the v3 API used until ef#38182. That shape conflates "aspect ratio" and "resolution tier" into a single value, which is awkward to author and reason about — devs naturally think --resolution 1080p and --aspect-ratio 16:9 independently. The flat preset has also caused 400s for npx hyperframes cloud render users trying the obvious shape.

This PR moves the CLI to match the v3 API's new decomposed shape so the two stay in sync. Combined with ef#38182, a user can now say hyperframes cloud render --resolution 4k --aspect-ratio 1:1 and have it render at 4K square instead of needing to remember --resolution square-4k.

How

Three files touched:

1. packages/cli/src/commands/cloud/render.ts — VALID_RESOLUTION changes to ["1080p", "4k"], new VALID_ASPECT_RATIO = ["16:9", "9:16", "1:1"], new --aspect-ratio arg in the command schema, parsed via parseEnumFlag, threaded through SubmitOptions and buildRenderBody into the request body as aspect_ratio.
2. packages/cli/src/cloud/_gen/types.ts — auto-regenerated from ef#38182's updated openapi/external-api.json. New HyperframesResolution = "1080p" | "4k" and HyperframesAspectRatio = "16:9" | "9:16" | "1:1" types; CreateHyperframesRenderRequest gains aspect_ratio?: HyperframesAspectRatio; HyperframesRenderDetail gains aspect_ratio?: HyperframesAspectRatio | null.
3. (Optional) packages/cli/src/cloud/_gen/client.ts — also regenerated but no semantic delta (the request body is passed through verbatim via the typed interface); skipped to keep the PR minimal.

The six legacy --resolution combinations map to the same effective output in the new shape — see the migration table in ef#38182's PR body. The new shape is strictly a smaller surface (3×2 = 6 cells exactly).

Pre-existing red CI

Test job fails on packages/engine/src/services/audioMixer.test.ts:122 (compensates amix normalization so multi-track master gain equals track count) — the test reads mixArgs[mixArgs.indexOf("-filter_complex") + 1] and expects "amix=inputs=3" but gets "-ss". Wrong arg-index assumption.

This is pre-existing on main, NOT introduced by this work. hf#1140 (Miguel's audio mixer fix, merged earlier) ALSO had Test fail in its CI checks — the test added by Magi in commit e7355703 passes locally per Magi's report but fails in CI because the actual ffmpeg arg layout differs from what the test assumes. This PR's diff is CLI-only (packages/cli/src/commands/cloud/render.ts + _gen/types.ts); it cannot affect packages/engine tests. Verified by inspection.

Cleanup PR needed against main from Magi or whoever owns the engine surface. Don't block this PR's review on it.

Test plan

• bunx oxlint, bunx oxfmt --check, bunx fallow audit --base origin/main, and cd packages/core && bunx tsc --noEmit && cd ../studio && bunx tsc --noEmit all green locally via lefthook pre-commit.

• Manual flag parsing: --resolution 1080p, --resolution 4k, --aspect-ratio 16:9 accepted; --resolution landscape (and other old presets), --aspect-ratio auto rejected with parseEnumFlag error.

• Existing cloud-render unit tests in packages/cli/src/cloud/*.test.ts (ansi, download, errors, parsing, poll) are unaffected by this change — none reference resolution directly.

• Unit tests added/updated — N/A; no cloud/render.test.ts exists today and the change is mechanical (flag plumbing). Will add coverage in the same PR that adds auto + 720p support (those need new paths worth pinning).

• Manual testing performed — flag-parse smoke per above.

• Documentation updated — packages/cli/src/docs/rendering.md doesn't reference the old presets, no doc update needed in this PR.

Deferred

720p, 4:5, 5:4, and auto are intentionally NOT in the new enum surface. They need render-pipeline capability additions (producer-side preset support for 720p/4:5/5:4, controller-side composition-dim inference for auto) — those will follow in a separate PR. The CLI will gain the same values when the API does.

— Created by Rames Jusso (hyperframes specialist, Rames team)

[miguel-heygen]

Clean flag plumbing — the CLI tracks the API shape exactly. camelCase → snake_case mapping is correct (aspectRatio → aspect_ratio), old preset values correctly rejected at parseEnumFlag before hitting the server.

Pre-existing engine test red is mine (wrong call index in the 3-track audioMixer test, not introduced by this diff). Fix is in #1144.