fix(sdk): apply AgentChat's maxDuration, region and lockToVersion

`AgentChat.ensureStarted` built its session config field by field and
never copied these three across, so anyone who set them on
`triggerConfig` got no error and no effect.

Author: 0ski

.changeset/agentchat-forward-trigger-config.md

@@ -0,0 +1,5 @@
+---
+"@trigger.dev/sdk": patch
+---
+
+Fixed `AgentChat` silently ignoring `maxDuration`, `region` and `lockToVersion` when they were set on its `triggerConfig`. They are now applied to the session's runs.

packages/trigger-sdk/src/v3/chat-client.ts

@@ -675,8 +675,14 @@ export class AgentChat<TAgent = unknown> {
       ...(this.triggerConfigDefault?.maxAttempts !== undefined
         ? { maxAttempts: this.triggerConfigDefault.maxAttempts }
         : {}),
-      // Not truthiness: `null` opts this chat out of pinning and must reach the resolver in
-      // `sessions.start`, which otherwise discovers an id from the environment.
+      ...(this.triggerConfigDefault?.maxDuration !== undefined
+        ? { maxDuration: this.triggerConfigDefault.maxDuration }
+        : {}),
+      ...(this.triggerConfigDefault?.region ? { region: this.triggerConfigDefault.region } : {}),
+      ...(this.triggerConfigDefault?.lockToVersion
+        ? { lockToVersion: this.triggerConfigDefault.lockToVersion }
+        : {}),
+      // Not truthiness: `null` opts out and must reach the resolver in `sessions.start`.
       ...(this.triggerConfigDefault?.externalDeploymentId !== undefined
         ? { externalDeploymentId: this.triggerConfigDefault.externalDeploymentId }
         : {}),