feat(cli): render --prores-profile picks ProRes 4444, hq, 422, lt or proxy for MOV - #6581

What changed

hyperframes render --format mov --prores-profile <4444|hq|422|lt|proxy>. 4444 is the default and unchanged (ProRes 4444, yuva444p10le, alpha). hq, 422, lt and proxy use prores_ks -profile:v 3/2/1/0 with yuv422p10le and no alpha.

• One table, PRORES_PROFILES in the engine, owns -profile:v, pixel format and whether the profile has alpha. getEncoderPreset takes the profile, and the distributed plan now asks it instead of hard-coding 4444.
• The profile flows through RenderConfig.proresProfile, the render request (proresProfile), the Docker run args, lambda render and the distributed plan. A plan with a non-default profile locks it in meta/encoder.json, so chunk workers rebuild the same preset. A 4444 plan is byte-identical to before (no new key).
• An unknown name is refused with the list (4444, hq, 422, lt, proxy), and so is --prores-profile on any format but mov. One validator, validateDeliveryEncoderConfig, for the local and the distributed path.
• A 422-family render prints one line: ProRes hq has no alpha channel: transparent areas render black. The CLI cannot know before capture whether a film is transparent, so it prints for every 422-family render.

What I measured

• Real renders on the devbox of a 640x360 transparent fixture, ffprobe of each file: default and 4444 give prores 4444 yuva444p12le; hq gives HQ yuv422p10le; 422 gives Standard yuv422p10le; lt gives LT yuv422p10le; proxy gives Proxy yuv422p10le. A transparent corner pixel in the hq file reads rgb 0,0,0. A 641x361 hq render succeeds (HQ 641x361 yuv422p10le).
• Refusals on the built CLI: --format mp4 --prores-profile hq and --prores-profile 422hq both exit with a usage error naming the list.
• Unit tests, 3 runs in a row on the devbox: engine chunkEncoder (109), producer deliveryEncoder + renderConfigValidation + the mov plan test + renderRequest (29), CLI utils and render (1650).
• fails without the fix: with chunkEncoder.ts from main the four new maps ProRes profile ... to -profile:v tests fail (4 failed, 105 passed).

What I did NOT exercise

• A real Lambda or Cloud Run render with a 422 profile. The plan locks the profile and the worker rebuilds the preset from it (covered by the mov plan test), but no chunked encode ran.
• The studio-server render route and the producer HTTP server do not take the option; this PR covers the CLI and the programmatic render request.
• Playing the 422 files in an editor.