Don't select first unsuccessful step when the pipeline is running

[stuartrowe]

Fixes #797.

Added a check if the run was complete when default selecting the first unsuccessful step in a pipeline.

Testing done

TODO - I need to figure out how use playwright to assert that the correct pipeline graph node is selected. Either one has some kind of -active class added to its div / a tag so maybe looking for that on the element with the expected id is the best approach.

NVM - all of the above already exists in the test util class PipelineOverviewPage.

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed

[felipecrs]

Works great!

chrome_UUXT2k7rUn.mp4

[stuartrowe]

I don't have much confidence in the tests as demonstrated by #800 (they pass with and without the fix).

I can reproduce #797 on my own production controller, but not on a local controller started with mvn hpi:run. Perhaps it's good enough that we now have the tests to prevent future regressions.

[timja]

Thanks!