Make selected log entries more AI-friendly

(from Dan Moseley)

when asking copilot in github to analyze a test failure, it pretty much always includes these two causes amongst its analysis:

1. Podman Not Found in Path:
Multiple errors indicate that the podman runtime is not installed or unavailable in the system's PATH, preventing it from being used.
Example log entry:
Code
"runtime status": { "ContainerRuntime": "", "runtime": "podman", "status": { "Installed": false, "Running": false, "Error": "exec: \"podman\": executable file not found in %PATH%..." }

2. Missing Environment Variable:
Tests fail due to a missing DEBUG_SESSION_PORT environment variable, which is required to start executables via the IDE.
Example log entry:
Code
Executables cannot be started via IDE: missing required environment variable 'DEBUG_SESSION_PORT'

I wonder whether it would be helpful/worthwhile to change DCP to use different wording so these didn't look like errors.. eg "To start executable via IDE, set 'DEBUG_SESSION_PORT' ... basically reduce noise

No files, tests, or entry points are named. Search the Go codebase for the Podman runtime and DEBUG_SESSION_PORT log messages, then review how they are emitted and tested. Done means the messages provide the same diagnostic guidance without being mistaken for test-failure causes.

Written by the indexing model from the issue text.