[Error Handling] - Small updates for failed test flow

[olha23]

Please check the video - https://www.loom.com/share/9a310b50170040e7a7cf227dc7603af5

Mockups - https://www.figma.com/file/LBN4SKVPq3ykegrPKbHT2Y/0.8-0.9-Release-Tracetest?node-id=2304%3A33723&t=ZsWKPfWjJromHfmG-1

[olha23]

also we need to add Run button near to failed test status:

[jorgeepc]

Hey @olha23 I merged a PR with the improvements, a couple of comments:

• For the issue about only seeing one log when the trace fails, we have a separate ticket Race condition not showing all events from the websocket #2340
• About the suggestion of adding an action/link in the message to help the user solve the issue, it's a little more complex. For example if the trace fails, we cannot recommend the user to go to the trigger page because the problem could be in the DataStore configuration and not the trigger data. In the epic we talked about this, and we have some notes about it but it deserves a larger conversation and planning.

Future troubleshooting features:

Be able to provide suggestions/recommendations to users based on events (errors).
Clients to have actions depending on event types

[olha23]

@jorgeepc agree with your point, but anyway we need to think for some call to action for the user who stuck with a problem. For each of problem we need to propose some action how to solve it.
@kdhamric also had some thoughts about this

[kdhamric]

I think we will discover improvements and areas to add better, deeper help as we go forward. As we do, we can create separate issues (or one bigger issue) for each one / group we identify.