Make debug counters available in non-assert builds as well

mlir/lib/Debug/DebugCounter.cpp

os << llvm::left_justify(counter->getKey(), 32) << ": {"
        << counter->second.countToStopAfter << "}\n";
   }
 }
 
 /// Register a set of useful command-line options that can be used to configure
 /// various flags within the DebugCounter. These flags are used when
 /// constructing a DebugCounter for initialization.
 void DebugCounter::registerCLOptions() {
-#ifndef NDEBUG
   // Make sure that the options struct has been initialized.
   *clOptions;
-#endif
 }
 
 bool DebugCounter::isActivated() {
   return clOptions->counters.getNumOccurrences() ||
          clOptions->printCounterInfo.getNumOccurrences();
 }
 
 // This is called by the command line parser when it sees a value for the

mlir/test/mlir-opt/debugcounter.mlir

 // This test exercises the example in docs/ActionTracing.md ; changes here
 // should probably be reflected there.
 
-// REQUIRES: asserts
 // RUN: mlir-opt %s -mlir-debug-counter=unique-tag-for-my-action-skip=-1 -mlir-print-debug-counter --pass-pipeline="builtin.module(func.func(canonicalize))" --mlir-disable-threading 2>&1 | FileCheck %s --check-prefix=CHECK-UNKNOWN-TAG
 // RUN: mlir-opt %s -mlir-debug-counter=pass-execution-skip=1 -mlir-print-debug-counter --pass-pipeline="builtin.module(func.func(canonicalize))" --mlir-disable-threading 2>&1 | FileCheck %s --check-prefix=CHECK-PASS
 
 func.func @foo() {
     return
 }
 
 // CHECK-UNKNOWN-TAG:  DebugCounter counters:
 // CHECK-UNKNOWN-TAG: unique-tag-for-my-action        : {0,-1,-1}
 
 // CHECK-PASS: DebugCounter counters:
 // CHECK-PASS: pass-execution                  : {1,1,-1}