Disable debug and trace logs at compile time when not DCHECK_IS_ON()

This will avoid debug and trace logs from shipping as part of an
official binary.

Bug: 339678662
Change-Id: Ibadcfadcfa0cf412831a8b6831bf7ada93269b45
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5972895
Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1375289}


CrOS-Libchrome-Original-Commit: c4ce7ab0119ef0445d777075120bcdfbace7e5d6

Author: danakj

base/logging/rust_log_integration.cc

@@ -19,22 +19,16 @@ BASE_EXPORT void print_rust_log(const char* msg,
                                 const char* file,
                                 int line,
                                 enum RustLogSeverity severity) {
-  // Drop debug and trace logs when DCHECK_IS_ON() is false. Otherwise, log them
-  // as info, since the C++ implementation lacks support for debug and trace
-  // logs.
-#if !DCHECK_IS_ON()
-  if (severity == RustLogSeverity::DEBUG ||
-      severity == RustLogSeverity::TRACE) {
-    return;
-  }
-#endif
-
   logging::LogSeverity log_severity;
   switch (severity) {
     case RustLogSeverity::DEBUG:
+      // Note that DEBUG level logs are dropped at compile time when
+      // DCHECK_IS_ON() is false. This is done through a Cargo feature.
       log_severity = logging::LOGGING_INFO;
       break;
     case RustLogSeverity::TRACE:
+      // Note that TRACE level logs are dropped at compile time when
+      // DCHECK_IS_ON() is false. This is done through a Cargo feature.
       log_severity = logging::LOGGING_INFO;
       break;
     case RustLogSeverity::INFO: