fix: handle large throughput writes

[mdonnalley]

Use console.log and console.error instead of process.stdout.write and process.stderr.write, to avoid losing information from back pressure on the streams

To replicate:

// write.js

import {stdout} from './src/ux/write.js'
const lines = Array.from(
  {length: 100},
  (_, i) =>
    `Line ${i} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer convallis fringilla sollicitudin. Nunc scelerisque neque non ipsum accumsan commodo. In et porttitor eros, ut vestibulum magna. Morbi felis diam, pharetra eu dui non, sollicitudin feugiat nisi. Aliquam cursus malesuada risus, vel luctus leo ornare sed. Morbi condimentum odio id ex facilisis bibendum. Nullam consectetur consectetur viverra. Donec nec ante dui. Integer lacinia facilisis urna vitae feugiat.`,
)

for (const line of lines) {
  stdout(line)
}

bun write.js

NOTE that the issue can only be replicated with bun - not node

Fixes #1177

@W-16645420@

[danielsharvey]

LGTM. I think it makes good sense to use console.log/console.error.

[danielsharvey]

Does it make sense to put a comment with the tests to provide context as to the motivation?
i.e. previous use of process.stdout/process.stderr had backpressure issues on Bun

[shetzel]

Using the repro script I saw skipped lines without the changes. With the changes no lines were skipped.