feat(host-contracts): fix mocked relayer edge case

Author: jatZama

host-contracts/test/asyncDecrypt.ts

@@ -106,13 +106,14 @@ const fulfillAllPastRequestsIds = async (mocked: boolean) => {
     if (!event) {
       throw new Error('Event is null');
     }
+    const counter =  event.args[0];
     const requestID = event.args[1];
     const handles = event.args[2];
     const contractCaller = event.args[3];
     const callbackSelector = event.args[4];
 
     // if request is not already fulfilled
-    if (mocked && !toSkip.includes(requestID)) {
+    if (mocked && !toSkip.includes(counter)) {
       // in mocked mode, we trigger the decryption fulfillment manually
       await awaitCoprocessor();
 
@@ -186,7 +187,7 @@ const fulfillAllPastRequestsIds = async (mocked: boolean) => {
         } else {
           console.log('Gateway fulfillment tx failed with an unknown error');
         }
-        toSkip.push(requestID);
+        toSkip.push(counter);
         throw error;
       }
     }

host-contracts/test/gatewayDecrypt/testAsyncDecryptMulti.ts

@@ -37,6 +37,6 @@ describe.only('TestAsyncDecryptMultiContracts', function () {
     const y = await this.contractA.yUint64();
     const y2 = await this.contractB.yUint64();
     expect(y).to.equal(0); // because first decryption callback reverted
-    expect(y2).to.equal(373737); // this second decryption, on the other hand, should succeed, but currently it is not fulfilled by mocked mode due to a logic bug in mocked relayer
+    expect(y2).to.equal(373737); // this second decryption, on the other hand, should succeed
   });
 });