Set machine size and maxDuration for a Trigger.dev v4 task, including per-run overrides and out-of-memory retries

Documented steps

1. Set the preset on the task: `export const heavyTask = task({ id: "heavy-task", machine: "large-1x", run: async ({ payload, ctx }) => {...} });` (https://trigger.dev/docs/machines).
2. Choose from the documented presets: micro 0.25 vCPU/0.25GB, small-1x 0.5/0.5 (default), small-2x 1/1, medium-1x 1/2, medium-2x 2/4, large-1x 4/8, large-2x 8/16.
3. Set a project-wide default in trigger.config.ts via the `machine` field (docs example: `export const config: TriggerConfig = { machine: "small-2x" }`).
4. Override per run at trigger time: `await tasks.trigger<typeof heavyTask>("heavy-task", payload, { machine: "large-2x" });`
5. Cap execution time with `maxDuration` in seconds — globally in trigger.config.ts, per task, or per trigger call (https://trigger.dev/docs/runs/max-duration).
6. Minimum `maxDuration` is 5 seconds; set `maxDuration: timeout.None` to disable the cap for a task or run.
7. Configure OOM escalation: `retry: { outOfMemory: { machine: "large-1x" } }`, and throw the SDK's `OutOfMemoryError` when you detect OOM yourself.
8. Inspect limits at runtime with `ctx.run.maxDuration` and `usage.getCurrent().attempt.durationMs`.