fix: Don't fail in apiMode when getting 404 not-founds on the build ID [CSR-3062]

[twk3]

Fixes #56

Description

There was a bug in our useAPI mode where we where erroring out the action for notFound. This was already fixed for sharding mode as part of the initial release, but was missed. Applied the same change to ensure the command doesn't fail the action.

Demo

Here is the log output from a sample run retry with this branch: https://github.com/twk3/playwright-gh-actions-demo/actions/runs/17507043195/job/49732490763 note the action passes and all tests are run again despite the 404 in the last-failed action log

Manual Testing

• You can reproduce the problem by enabling useApi: true, and setting previous-ci-build-id to something that isn't the actual build Id. (though the previous ci build id template doesn't have to be wrong for this to happen in the real world, the run just has to have not been created, maybe there was nothing to do, etc).
• Without this change
  • The server throws a 404 for the missing run, and the action fails
• With this change
  • The server throws a 404 for the missing run, but the action doesn't fail, and instead there is no last-run file. So playwright will start running all the tests. (which is the safest option)

[notion-workspace]

🔍 check useAPI last-failed action isn’t halting the CI pipelines.

[Copilot]

Pull Request Overview

This PR fixes a bug in API mode where the action would fail when receiving 404 not-found responses for build IDs. The fix applies the same error handling approach that was already implemented for sharding mode.

• Adds ignoreReturnCode: true option to the exec.exec() call in API mode
• Ensures the action doesn't fail when the API returns a 404 for non-existent build IDs
• Aligns error handling behavior between API mode and sharding mode

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[vCaisim]

@twk3 nice job!