Relates to CODAGT-1330
When chatd prepares a turn for a chat with a workspace, it looks up the
chat's agent so the agent binding is up to date before anything uses it.
That lookup dropped every error, so a failed database read looked the
same as a chat with no agent, and the turn carried on with whatever
binding the chat already had. If reading the chat's bound agent failed,
we'd also log it and resolve a new agent from scratch. Separately, a
failed read of the computer use provider setting hid the `computer_use`
subagent type from `spawn_agent` for that turn.
To fix, we'll just return the database error, so the prepare retry runs.
Not having a usable agent is still a normal result, e.g. the chat has no
workspace, the workspace was deleted, or more than one agent uses the
chat suffix, so a broken template doesn't fail every turn. A computer
use provider we don't recognise still just makes `computer_use`
unavailable.
This follows on from #30492.