Improve Nomad Docs

[mpass99]

to describe the behavior of running executions during Nomad restarts.

Related to #651

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.19%. Comparing base (d83407e) to head (f72f611).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #660   +/-   ##
=======================================
  Coverage   76.19%   76.19%           
=======================================
  Files          43       43           
  Lines        3592     3592           
=======================================
  Hits         2737     2737           
  Misses        625      625           
  Partials      230      230           

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

[MrSerth]

Would you mind to copy the table added in #651 (comment)? This might be helpful and summarizes our findings.

Further, I was wondering about a "consequence" after a problematic restart. Shouldn't be there some note on the runner being clean / used / marked as used (in case an agent is restarted)? And maybe a word on the coupling of the Nomad service and Docker service that we added (to restart one if the other restarts). For servers, I would love to see another sentence about reconnecting, recovering the event stream, ...

By the way, the event stream usage (the why, the benefits, the pitfalls) is not yet documented here either, is it? Just saying that this might be useful, too, especially as a handover.

[MrSerth]

Thank you, so much! This makes the documentation much more valuable and I you greatly addressed all my previous review points. A few minor comments left, but nothing big.

[MrSerth]

I am continue to feed my issue #669, but I assume those should be fixed soon with your latest PR.

[MrSerth]

Thanks for taking the time to write additional documentation; I really appreciate it! 🌍