Red herring logs

When running plans on i15-1 we get occassional logs of:
* `Invalid correlation id detected: None` (https://graylog.diamond.ac.uk/messages/graylog-prod_33/d3cf3640-73c5-11f1-9050-ba072096fdc1)
* `Invalid type ... in attribute 'msg.args' value sequence. Expected one of ['bool', 'str', 'bytes', 'int', 'float'] or None` (https://graylog.diamond.ac.uk/messages/graylog-prod_33/03bca6d1-73c6-11f1-9050-ba072096fdc1)

These seem to cause no actual issues on the beamline but confuse support staff trying to diagnose other issues

## Acceptance Criteria
- The above error logs are removed (or at least reduced to debug)

Start by reproducing a plan on i15-1 and search the codebase for the exact messages "Invalid correlation id detected" and "Invalid type". Trace which logging paths emit them, then verify that the messages are removed or reduced to debug without affecting beamline operation.

Written by the indexing model from the issue text.