Revert of [Telemetry] Disable DCHECK crashes in release builds.

tools/telemetry/telemetry/core/backends/chrome/chrome_browser_backend.py

Index: tools/telemetry/telemetry/core/backends/chrome/chrome_browser_backend.py
diff --git a/tools/telemetry/telemetry/core/backends/chrome/chrome_browser_backend.py b/tools/telemetry/telemetry/core/backends/chrome/chrome_browser_backend.py
index cc9d4378064bcb62097d4d6df5b49aca4d38c94f..497ac73bcfdaf4e8ce4251237a9e45032255db75 100644
--- a/tools/telemetry/telemetry/core/backends/chrome/chrome_browser_backend.py
+++ b/tools/telemetry/telemetry/core/backends/chrome/chrome_browser_backend.py
@@ -88,15 +88,6 @@
     args.append('--metrics-recording-only')
     args.append('--no-default-browser-check')
     args.append('--no-first-run')
-
-    # TODO(tonyg): Telemetry runs on release build bots which enable DCHECKs.
-    # While, we'd really like for Chrome to be DCHECK clean, pragmatically, it
-    # is far from it and the Telemetry unittests are hitting DCHECKS so often
-    # that the flakiness is becoming untenable.
-    #
-    # We should remove this as soon as we're ready to get serious about the
-    # DCHECK problem and keep Chrome clean.
-    args.append('--silent-dump-on-dcheck')
 
     # Turn on GPU benchmarking extension for all runs. The only side effect of
     # the extension being on is that render stats are tracked. This is believed