fix(error): propagate render error message to TUI

[zanjonke]

Summary

• pass the render context's last error message into RenderError.get_display_message()
• ensure the TUI receives the actual render failure message instead of the previous action payload

Testing

• not run; PR created from existing commit

[NejcS]

Your change is fixing the same problem that I fixed with the last pushed commit (6c0af01#diff-249ce6ec60216cf960c2d236774c3f21b47f4d91bdd98151833332b127b26174R36).

My two cents: I don't think we should be using the last action's payload to get the error message. So my solution was lazy (it made it work but it didn't improve the solution)

But I also think that your change is not the better option (you are now passing code_renderer.render_context.last_error_message twice into the get_display_message function.

I'll come up with a better solution in the near future.

[NejcS]

Ah and the problem that I fixed in the referenced commit from the previous comment is that the output was something like "cannot display dict when expecting a string" in case I hit the 20 attempts limit for conformance tests. What I did is I went through all actions to find "failing" outcomes and I made sure that all instances of such outcomes are also returning RenderError.encode(message=error_msg).to_payload(), ... there were just 2 left.

[zanjonke]

This was solved in #217. Thanks @NejcS .