fix(react-hooks): reject more than two named limits instead of truncating

Matches the SDK's trigger validation, and the shared changeset now
versions react-hooks alongside sdk and core.

Author: matt-aitken

.changeset/task-concurrency.md

@@ -1,6 +1,7 @@
 ---
 "@trigger.dev/sdk": patch
 "@trigger.dev/core": patch
+"@trigger.dev/react-hooks": patch
 ---
 
 Control a task's concurrency with the new `concurrency` option, and share limits across tasks with named concurrency limits. An inline shape caps the task itself; `concurrencyLimit()` declares a limit any task can hold (up to two named limits per task), and a trigger call can switch a run's named limits with its own `concurrency` option.

packages/react-hooks/src/hooks/useTaskTrigger.ts

@@ -75,12 +75,15 @@ export function useTaskTrigger<TTask extends AnyTask>(
 
     const queueName = options?.queue;
     const concurrency = options?.concurrency
-      ? (Array.isArray(options.concurrency) ? options.concurrency : [options.concurrency]).slice(
-          0,
-          2
-        )
+      ? Array.isArray(options.concurrency)
+        ? options.concurrency
+        : [options.concurrency]
       : undefined;
 
+    if (concurrency && concurrency.length > 2) {
+      throw new Error("The concurrency option accepts at most two named limits.");
+    }
+
     const handle = await apiClient.triggerTask(id, {
       payload: payloadPacket.data,
       options: {