Fix issue with large error msgs

[tomsmith8]

Cap excessive error message size in Agent logs

Issue:
Agent updates are currently producing extremely large error messages, particularly in cases such as login failures or ontology mismatches. These logs include full serialized JSON responses and internal states, resulting in:

• Bloated and unreadable log output (see screenshot).
• Poor developer experience when debugging.
• Potential UI performance issues due to oversized log payloads.

Screenshot Example:

Proposed Solution:

• Introduce a character or payload size cap for error logs shown in the Agent update panel.
• Display a truncated version of long logs by default, with an optional “View full details” toggle or expandable section.
• Ensure critical information remains visible (e.g., top-level error message, query input, tool name).

---

Acceptance Criteria:

• Logs exceeding the defined cap are trimmed with an ellipsis and/or "Show more" control.
• Key debugging data is preserved in the initial view.
• Log display no longer causes horizontal scroll or layout issues in the UI.
• Performance remains stable regardless of error log size.

---

[Ekep-Obasi]

@tomsmith8 please assign me

[aliraza556]

@tomsmith8 Please assign me