Do not block job from running on runner hooks

[tcarmet]

A softer approach to the job started hook checks that runs systematically.
To avoid a situation where those hook might do more harm than good, if they continuously fail after a certain amount of tries, release the runner and let it do its thing.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.72%. Comparing base (50efe19) to head (f475118).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #678   +/-   ##
=======================================
  Coverage   86.72%   86.72%           
=======================================
  Files          34       34           
  Lines        1431     1431           
=======================================
  Hits         1241     1241           
  Misses        190      190           

Flag	Coverage Δ
api	64.91% <ø> (ø)
unit	67.43% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[liaud]

Thank you! I wonder why it couldn't be started in the first place but errors should already be logged, not sure where it went through 🤔

[tcarmet]

Thank you! I wonder why it couldn't be started in the first place but errors should already be logged, not sure where it went through 🤔

If I remember well it was stuck trying to check if docker was up. Which could be an issue later in the build, but it's better not to get the job blocked for hours due to this. Might as well fail and re-run the job.