Agentic chat stop button should be more graceful

Problem

When investigating connection issues in &19253 (comment 2734636181) I found that the stop button in agentic chat does not seem to behave as well as the stop button in our flows. The agentic chat button results in errors being logged/tracked in workhorse. This means that normal user behaviour ends up being logged as an error and this is creating noise in the logs that makes it difficult to track actual error cases (e.g. disconnects).

Solution

Investigate why the flow disconnects more gracefully and see if we can implement the same mechanism for disconnecting in agentic chat.