Run view - Show real status names

[Ark-kun]

We must show real status names in the execution node titles and node details.
Currently status names often do not correspond to a real status. For example, "Pending" instead of "Waiting for upstream".

The real statuses are

• Queued (Orchestrator has not attempted to launch the execution yet)
• Waiting for upstream (can be shortened if it breaks UX; )
• Pending (job is created in external execution system, but container has not started yet (and may never start if something is wrong (container image, insufficient resources)))
• Running
• Succeeded
• Failed
• System error
• Skipped
• Cancelled

graph TD;
  Queued --> Waiting_for_upstream;
  Queued --> Pending;
  Pending --> Running;
  Running --> Succeeded;
  Running --> Failed;
  Running --> Cancelled;
  Waiting_for_upstream --> Skipped;
  Waiting_for_upstream --> Pending

  Queued --> System_error;
  Pending --> System_error;
  Running --> System_error;

Loading

Tech Doc about statuses

[Volv-G]

Hard "disagree" on my part - we can have a mapping, but no texts coming from the backend should be shown as is in the UI - this kills any opportunity for localization and introduces additional design challenges - changes in the backend might cause UI degradation.

[Ark-kun]

I'm not against localization. But we should not completely change the meaning of the statuses.
We have many threads where incorrect statuses puzzle/mislead the users. Example: "That node waiting for upstream. Why doesn't it recognize that the upstream has finished".
And this has already puzzle/mislead myself too on multiple occasions.

[maxy-shpfy]

Ref:

• Refactor, unify and consolidate various Status logic
• Unify Status Icons and Logic