test(rest): give the nested-relation cap case a 30 s budget (ported fix for #27037)

The case seeds RELATION_FILTER_ID_CAP (1,000) rows and deletes 1,001: 2.3 s
alone, past the default 5 s on a loaded full-suite queue shard, which
ejected #26960, #27011 and #27020 (#27037). The slowdown itself is
#27004's (since #26930 a 1,001-row predicate delete is about 18x slower);
this only budgets for it.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QUs3Bshfmr8srPY21BVS4u
(cherry picked from commit 6674ba8)

Author: claude

packages/rest/src/data-nested-object-door.test.ts

@@ -309,7 +309,8 @@ for (const cell of CELLS) {
           await engine.delete(OBJECT, { where: { id: 'd_cap' } } as any);
           await engine.delete(OWNER, { where: { region: { $in: ['CAP', 'CAP_EXTRA'] } }, multi: true } as any);
         }
-      });
+        // Budget for the 1,000-row seed and its 1,001-row delete on a loaded full-suite shard (#27037); the slowdown itself is #27004's.
+      }, 30_000);
 
       it('CONTROL the routes still answer the rows, and a file field\'s object reaches the driver unjudged', async () => {
         const na = await query({ where: { region: 'NA' } }, OWNER);