fix: widen the controllerTransfer pending-instruction poll

The last CI run reached 250 of 257 tests passing, with this the only
genuine failure: "the counter party should have the instruction as
pending".

Blocks are 6s on the runner, measured over 322 blocks of the run, so the
10 x 2s retry window covered only about three of them. The counter
party's pending list comes from the middleware, which lags the chain
further under load, and three blocks was not reliably enough with eight
workers competing. Its sibling in sdk/settlements/tradeAssets.ts does
the same lookup with no retry at all and passes, so this is a timing
margin rather than a logic fault.

Poll for 30 attempts instead, covering ten blocks, still well inside the
50 block (~300s) validity getPendingInstructionEndBlock allows.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: F-OBrien

tests/src/sdk/assets/controllerTransfer.ts

@@ -49,8 +49,14 @@ export const fungibleAssetControllerTransfer = async (
   await awaitMiddlewareSynced(transferTx, sdk, 30, 3000);
 
   // affirm instruction
+  //
+  // Blocks are 6s, so the old 10 x 2s window only covered about three of them.
+  // The counter party's pending list is served by the middleware, which lags
+  // the chain further under load, and on a busy CI runner three blocks was not
+  // reliably enough. 30 attempts covers ten blocks, still far inside the ~300s
+  // (50 block) validity `getPendingInstructionEndBlock` gives the instruction.
   let counterInstruction;
-  for (let attempt = 0; attempt < 10; attempt++) {
+  for (let attempt = 0; attempt < 30; attempt++) {
     const { pending } = await counterParty.getInstructions();
     counterInstruction = pending.find(({ id }) => id.eq(instruction.id));
     if (counterInstruction) {