[Feat] Track settled task outcomes

[roomote-roomote]

Opened on behalf of Bruno Bergher. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

Centralized task_settled capture by task-run ID and extended it to direct cancellation paths. Analytics-disabled deployments now return before loading the task run.

Why this change was made

Anonymous analytics should not perform task-run reads when the deployment has opted out.

Impact

Opted-out deployments perform no task-settlement telemetry work beyond the analytics setting check; enabled deployments keep the same anonymous lifecycle tracking.

[roomote-roomote]

No new code issues found. See task

• packages/sdk/src/server/lib/task-runs/finish-run.ts:259: task_settled is emitted only from finishRun and selected dequeue/bootstrap paths. Direct terminal cancellations (for example cancelTaskRunDirect used by the no-sandbox stop flow, queue enqueue failures and evictions, and cancelLinearTaskRun) bypass all of them, so canceled runs remain absent from the event despite the new all-outcomes contract. Centralize the terminal emission or cover each direct-cancel writer.

_{Reviewed ba23875}