test(core): drop the timing assertion from the zodIpc ack test

The `resolves` assertion already fails when the ack is rejected, and a
wall-clock bound could flake on a slow runner. Also hyphenate the
changeset's compound adjectives.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Author: NERLOE

.changeset/void-ipc-acks.md

@@ -2,4 +2,4 @@
 "@trigger.dev/core": patch
 ---
 
-Fix a ~6 second delay between a task finishing and its run completing (and a ~31 second delay when cancelling a run) in projects that use zod 4.4 or newer.
+Fix a ~6-second delay between a task finishing and its run completing (and a ~31-second delay when cancelling a run) in projects that use zod 4.4 or newer.

packages/core/test/zodIpc.test.ts

@@ -66,11 +66,9 @@ describe("ZodIpcConnection", () => {
   it("resolves sendWithAck for a void callback after the ack crosses a JSON boundary", async () => {
     const connection = createConnections();
 
-    const start = Date.now();
     await expect(connection.sendWithAck("FLUSH", { timeoutInMs: 1000 }, 1000)).resolves.toBe(
       undefined
     );
-    expect(Date.now() - start).toBeLessThan(500);
   });
 
   it("resolves sendWithAck with the callback payload", async () => {