fix: do not check if the previous state is "started"

Solves the following scenario:
- Publisher triggers a workflow run
- Workflow pings Publisher back with "started" state
- Publisher isn't yet available via http (probably due to some Lagoon delays)
- Publisher does not receive "started" state
- After a full build Publisher receives "finished" state
- Yet, because of "previous === 'started'" check, it does not react to it
- So it waits for the timeout and then, after the timeout is fired, starts a new full build

Author: Leksat

packages/npm/@amazeelabs/publisher/src/mode-github-workflow/tasks.ts

@@ -4,7 +4,6 @@ import {
   ApplicationState,
   WorkflowPublisherPayload,
 } from '@amazeelabs/publisher-shared';
-import { pairwise } from 'rxjs';
 
 import { getConfigGithubWorkflow as config } from '../tools/config';
 import { saveBuildInfo } from '../tools/database';
@@ -107,27 +106,23 @@ async function runWorkflow(args: {
     }
 
     const subscription = core.state.workflowState$
-      .pipe(pairwise())
-      .subscribe(([previous, current]) => {
-        if (current === 'started') {
+      .subscribe((state) => {
+        if (state === 'started') {
           core.output$.next('Workflow started', 'info');
           core.output$.next('Logs: ' + core.state.workflowRunUrl);
           return;
         }
-        if (
-          previous === 'started' &&
-          (current === 'success' || current === 'failure')
-        ) {
+        if (state === 'success' || state === 'failure') {
           subscription.unsubscribe();
-          if (current === 'success') {
+          if (state === 'success') {
             core.output$.next('Workflow succeeded', 'success');
           } else {
             core.output$.next('Workflow failed or cancelled', 'error');
           }
           core.output$.next('Logs: ' + core.state.workflowRunUrl);
 
           clearTimeout(timeout);
-          return resolve(current === 'success');
+          return resolve(state === 'success');
         }
       });
   });