Improve logging output to provide cleaner errors and which node

### Description

Raised during Developer Demo

> Error messages in Node-RED logs are just a JSON String (no indication of which node)
> ```
> 08/08/2025 10:27:13 [info] Started flows
> 08/08/2025 10:27:15 [error] {"length":103,"name":"error","severity":"ERROR","code":"42703","position":"70","file":"parse_relation.c","line":"3716","routine":"errorMissingColumn"}
> 08/08/2025 10:27:30 [info] Stopping flows
```

### Epic/Story

_No response_

The issue names no file, test, or entry point. Start by reproducing the Developer Demo error in Node-RED and locating where the JSON error is logged; done means the logs show a readable error and identify the node responsible.

Written by the indexing model from the issue text.