trigger-workflow-dispatch: accommodate for clock skew

Seems as if the date we get in the response when creating a workflow
dispatch _might_ be at, or after, the date the corresponding workflow
run is created. Most likely explanation: clock skew. Let's allow for
that.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Author: dscho

GitForWindowsHelper/trigger-workflow-dispatch.js

@@ -47,7 +47,9 @@ const triggerWorkflowDispatch = async (context, token, owner, repo, workflow_id,
         { ref, inputs }
     )
 
-    const runs = await waitForWorkflowRun(context, owner, repo, workflow_id, new Date(date).toISOString(), token)
+    // to avoid any potential clock skew, we set the "after" time to 5 seconds before the current time
+    const after = new Date(Date.parse(date) - 5000).toISOString()
+    const runs = await waitForWorkflowRun(context, owner, repo, workflow_id, after, token)
     return runs[0]
 }