TabUsageRecorder::Initialize has a DCHECK to make sure that it only gets run once, but several tests in ChromeBrowserMainExtraPartsMetricsTest call ChromeBrowserMainExtraPartsMetrics::PostBrowserStart, which will call TabUsageRecorder::Initialize

When multiple of these tests are run at once, the later runs will crash, but then succeed on retry.  This should be fixed to avoid the crash.