Detection of yarn does not work (anymore?)

Describe the bug

While loopback-cli tries to detect yarn a file yarn-error.log is generated. It seems that yarn cannot write to it's stdout when it is spawned as a child process by lb4.

Logs

yarn-error.log:

Arguments: 
  /snap/node/7382/bin/node /snap/node/7382/bin/yarn.js help

PATH: 
  /usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

Yarn version: 
  1.22.19

Node version: 
  19.9.0

Platform: 
  linux x64

Trace: 
  Error: EACCES: permission denied, write
      at writeSync (node:fs:938:3)
      at SyncWriteStream._write (node:internal/fs/sync_write_stream:26:3)
      at writeOrBuffer (node:internal/streams/writable:392:12)
      at _write (node:internal/streams/writable:333:10)
      at Writable.write (node:internal/streams/writable:337:10)
      at module.exports.Command.outputHelp (/snap/node/7382/lib/cli.js:58339:18)
      at module.exports.Command.help (/snap/node/7382/lib/cli.js:58350:8)
      at Object.run (/snap/node/7382/lib/cli.js:83978:13)
      at run (/snap/node/7382/lib/cli.js:88392:22)
      at /snap/node/7382/lib/cli.js:88722:16

npm manifest: 
  No manifest

yarn manifest: 
  No manifest

Lockfile: 
  No lockfile

Additional information

This issue can be fixed by using stdio: 'ignore' instead of stdio: false here: https://github.com/loopbackio/loopback-next/blob/9d99c620e7dedad9099e1c83a068216c198749e0/packages/cli/lib/utils.js#L768

Reproduction

none

Comienza en packages/cli/lib/utils.js, alrededor de la línea 768, donde se inicia yarn durante la detección, y compara la configuración actual de stdio con el cambio sugerido en el issue. Verifica que la detección de yarn ya no produzca yarn-error.log ni un fallo EACCES de stdout cuando se ejecuta como proceso hijo de lb4; no se proporciona ninguna reproducción ni archivo de prueba.