fix Windows replacement for process kill during deployment

The old Windows rule matched 'Exit code: [KILLED]' which was never present
because 'Exit code: 1' (Windows exit code for kill) was never normalized to
'[KILLED]' -- the [KILLED] normalization only fires via exit code 137 (Linux)
or after [PROCESS_KILLED] is already inserted.

Match 'Exit code: 1' directly (the raw Windows exit code), then insert
[PROCESS_KILLED] and normalize in one step.

Co-authored-by: Isaac

Author: denik

acceptance/bundle/deploy/wal/test.toml

@@ -30,9 +30,9 @@ Old = '(\[PROCESS_KILLED\]\n\nExit code: )1'
 New = '${1}[KILLED]'
 
 # On Windows, no bash "Killed" message appears when CLI has produced output before termination.
-# Insert [PROCESS_KILLED] between last output line and exit code for consistency.
+# Match the raw exit code 1 (Windows never gets 137 or [PROCESS_KILLED] marker first).
 [[Repls]]
-Old = '(Deploying resources\.\.\.)\n\nExit code: \[KILLED\]'
+Old = '(Deploying resources\.\.\.)\n\nExit code: 1'
 New = """${1}
 [PROCESS_KILLED]