Some automation failures in the Windows CI do not fail the build

[mokagio]

I don't know where the issue lies, if in the way we call the scripts, if in how Buildkite runs them from the root, or elsewhere. Notice the logs in this build:

[2024-11-04T01:31:45Z] file:///C:/buildkite-agent/builds/ci-windows-i-08444a988c914038f-1/automattic/studio/scripts/confirm-tag-matches-version.mjs:17
[2024-11-04T01:31:45Z] 	throw new Error( 'Build was not triggered by a new tag' );
[2024-11-04T01:31:45Z] 	      ^
[2024-11-04T01:31:45Z]
[2024-11-04T01:31:45Z] Error: Build was not triggered by a new tag
[2024-11-04T01:31:45Z]     at file:///C:/buildkite-agent/builds/ci-windows-i-08444a988c914038f-1/automattic/studio/scripts/confirm-tag-matches-version.mjs:17:8
[2024-11-04T01:31:45Z]     at ModuleJob.run (node:internal/modules/esm/module_job:217:25)
[2024-11-04T01:31:45Z]     at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
[2024-11-04T01:31:45Z]     at async loadESM (node:internal/process/esm_loader:34:7)
[2024-11-04T01:31:45Z]     at async handleMainPromise (node:internal/modules/run_main:66:12)
[2024-11-04T01:31:45Z]
[2024-11-04T01:31:45Z] Node.js v20.9.0
[2024-11-04T01:31:46Z] Verifying Windows 10 SDK location...

When confirm-tag-matches-version.mjs threw, the CI job should have failed. Yet it continued.