fix: defer cmd log to respect .quiet()/.verbose() overrides

[hobostay]

Summary

• Fixes Changed output behavior when using quiet and verbose in version 8.2.0 #931
• Defers the cmd log entry in ProcessPromise.run() with queueMicrotask() so that chained .quiet() / .verbose() overrides take effect before the log is emitted

Problem

Since PR #914 removed the setImmediate around run(), the start event fires synchronously during run(), which is called before chained methods like .quiet() or .verbose() can modify the snapshot. This means the cmd log entry always uses the original verbose/quiet state, ignoring per-call overrides.

Observed behavior:

• .quiet() does not suppress the command line output
• .verbose(false) does not suppress the command line output
• .quiet(false) does not enable the command line output when $.quiet = true
• .verbose(true) does not enable the command line output when $.verbose = false

Fix

Instead of reverting the setImmediate removal (which was needed for pipe splitting), this PR defers only the cmd log entry using queueMicrotask(). This is more targeted:

• The process still starts synchronously (no change to spawn timing)
• queueMicrotask runs after the current synchronous call stack completes but before any I/O, so chained methods have already executed
• The timeout setup remains synchronous for correct timing

Test plan

• Added 4 new test cases covering all .quiet()/.verbose() override scenarios from Changed output behavior when using quiet and verbose in version 8.2.0 #931
• All 264 existing passing tests continue to pass (6 pre-existing failures unrelated to this change)

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.