Add worker console messages (write/writeln) alongside ProgressBar

[devin-ai-integration]

Summary

This PR adds write()/writeln() to ParallelWorker so workers can emit console messages while a ProgressBar is active, without the bar overwriting them.

How it works

• ParallelWorker gains write()/writeln() via CommunicatesWithProgressBarWorker.
• Calls are sent as a new WriteOutputMessage command to the Runner thread.
• The Runner owns the Symfony ProgressBar and a StreamOutput on php://stderr.
• When the bar is active, Runner does clear() → write the message → display(); otherwise it writes directly.
• setMessage()/advance() keep working as before; memory and items-per-second stats continue to be updated on the same bar.

Why the Runner owns the output

The RFC originally explored a separate ConsoleWorker/progress thread, but routing everything through the existing Runner channel keeps the coordinator in one place and avoids sharing STDERR across threads. The Runner main thread is the only place that writes to php://stderr.

Tests

• testThatWorkerCanWriteMessagesWithoutProgressBar spawns a separate PHP process and verifies Starting #n/Done #n messages.
• testThatWorkerCanWriteMessagesWithProgressBar verifies the messages are interleaved with progress-bar redraws and the bar reaches 3 of 3:.

Notes

• No BC break: Contracts\ParallelWorker is unchanged; the methods are added on the abstract ParallelWorker class.
• CI opcache.jit is disabled because JIT + ext-parallel can deadlock.

Link to Devin session: https://app.devin.ai/sessions/aa44109acb6346c2abd6b14c45072be7
Requested by: @hschimpf

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[hschimpf]

Requesting changes pending a few cleanups:

1. tests/ParallelTest.php still has debug fwrite(STDOUT, ...) in setUp/tearDown/runWorkerScript that should be removed or gated.
2. testThatWorkerCanWriteMessagesWithProgressBar only asserts substring presence; add ordering/negative assertions to prove messages are not overwritten by the bar.
3. The @file_put_contents('php://stderr', ...) fallback in CommunicatesWithProgressBarWorker should use fwrite(STDERR, ...) instead and drop @.
4. Update docs/RFC-progressbar-console-messages.md implementation outline to match the final Runner-owned design.
5. Please resolve/answer the open threads about ConsoleOutput → StreamOutput and the trait name mismatch.

Once those are addressed, this looks good to merge.