(context: I asked about this originally at #7199)

Describe the feature you'd like to request

I'd like to have different output modes in development and CI:

• In development, I want logs to behave like new-only.
  • As someone responsible for the build, I want it to be clearer when I'm getting unexpected cache misses. new-only makes it easy for me to see.
  • For people running builds, I want them to know when they're getting the cached build speedups we've been working so hard to achieve.
• In CI, I want logs to behave like full:
  • I want to see the exact steps taken to make it easer to debug failed builds.

Describe the solution you'd like

I would like Turbo to read a TURBO_OUTPUT_MODE or similar environment variable with one of the values of outputMode/--output-logs and use that to inform the output it creates.

In cases where there are conflicts between the sources of configuration, Turbo would chose the first of:

1. --output-logs on the command line
2. TURBO_OUTPUT_MODE in the environment
3. outputMode in the configuration
4. the default output mode (which I'm not proposing any change to)

Describe alternatives you've considered

• Setting outputMode in my root turbo.json: I could do this programmatically when starting CI, but it seems sketchy to mess around with the source in CI and I don't want to break caching.
• Setting --output-logs on all calls: As part of incremental migration to Turbo, I have several places where Turbo calls an old build tool (Gulp) and is called in turn. Since these are nested, I'd have to pass along the --output-logs value in all cases, leading to a lot of rewiring and the opportunity to get it wrong.
• Overwriting the global turbo: only works if my build only calls turbo and resolves from PATH instead of referencing an absolute path. Probably fairly reliable, but still feels like a hack to me.

I think setting an environment variable is superior to all these solutions, since it can be set once-for-all. Without any modifications or hacks.