[Design] Show browser logs for failed journeys/steps

[hmdhk]

Summary of the problem (If there are multiple problems or use cases, prioritize them)
Showing browser logs helps users investigate failed journeys.

User stories
As a user who is investigating a journey failure, it's helpful to know what browser logs exist before the failure.
The browser logs are captured in the agent with this PR and they include text and type fields.

List known (technical) restrictions and requirements
The number of browser logs should be limited to a reasonable number of most recent logs with the ability to expand further to see older ones.

Note: The browser logs are only captured for failed journeys.

cc @katrin-freihofner @drewpost @paulb-elastic @andrewvc

[elasticmachine]

Pinging @elastic/observability-design (design)

[drewpost]

I think this is a serious usability improvement. I'd be a big fan of prioritising this.

[katrin-freihofner]

I think this is solved by elastic/kibana#80156

[hmdhk]

@katrin-freihofner, just to clarify, this issue is for browser logs (which potentially should be displayed for failed steps), are you implying that we will use the same design for agent logs for browser logs as well?

[katrin-freihofner]

@jahtalab would you mind adding an example for both just to make sure I understand the issue at hand?

[paulb-elastic]

Don't we have them both in the current design, or is there another set of logs?