buck2: don't output stdout in red for no reason

Summary:
We leave stderr in whatever color we received it in, but for some reason
we print stdout in red. This is rather confusing. Don't do that.

Reviewed By: lmvasquezg

Differential Revision: D47231602

fbshipit-source-id: 777c0558bb5418f2d569e02ed89524aa9b82e97b

Author: krallin

app/buck2_client_ctx/src/subscribers/superconsole.rs

@@ -831,10 +831,7 @@ fn lines_for_command_details(
             .with(Color::DarkRed)
             .attribute(Attribute::Bold),
     )]));
-    lines.extend(Lines::from_multiline_string(
-        &command_failed.stdout,
-        color(Color::DarkRed),
-    ));
+    lines.extend(Lines::from_colored_multiline_string(&command_failed.stdout));
     lines.push(Line::from_iter([Span::new_styled_lossy(
         "stderr:"
             .to_owned()
@@ -859,13 +856,6 @@ fn truncate(contents: &str) -> Option<String> {
     }
 }
 
-fn color(color: Color) -> ContentStyle {
-    ContentStyle {
-        foreground_color: Some(color),
-        ..Default::default()
-    }
-}
-
 #[cfg(test)]
 mod tests {
     use std::time::SystemTime;