Better detect errors in certain job steps and stop/fail gracefully

from: https://github.com/CommunityToolkit/Tooling-Submodule/actions/runs/4421712339/jobs/7752798063


Instead currently this sat for over an hour spinning without showing output... oops

Low-pri right now, but wanted to track for future.

Start with the linked GitHub Actions job run and inspect the job steps around the hour-long spin, using the attached screenshot for context. Identify the step that fails to report output or terminate; done means the workflow detects that error and stops or fails gracefully instead of continuing indefinitely.

Scritto dal modello di indicizzazione a partire dal testo della issue.