Get rid of kDistinctModuleDatabaseSequence

The feature has been enabled by default for a while now and things are
working great.

Bug: 943303
Change-Id: I47576be44ffa92b081b65df132c6bc67a3dbca2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017990
Auto-Submit: Patrick Monette <pmonette@chromium.org>
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#735199}

chrome/browser/win/conflicts/module_database.cc

@@ -109,20 +109,11 @@ ModuleDatabase::~ModuleDatabase() {
 
 // static
 scoped_refptr<base::SequencedTaskRunner> ModuleDatabase::GetTaskRunner() {
-  static constexpr base::Feature kDistinctModuleDatabaseSequence{
-      "DistinctModuleDatabaseSequence", base::FEATURE_ENABLED_BY_DEFAULT};
-
-  static base::LazySequencedTaskRunner g_distinct_task_runner =
+  static base::LazySequencedTaskRunner g_module_database_task_runner =
       LAZY_SEQUENCED_TASK_RUNNER_INITIALIZER(
           base::TaskTraits(base::ThreadPool(), base::TaskPriority::BEST_EFFORT,
                            base::TaskShutdownBehavior::CONTINUE_ON_SHUTDOWN));
-
-  // A new task runner to the UI thread can be "created" every time in the
-  // disabled arm, in practice it's always the same task runner (it doesn't need
-  // a lazy instance to a privately owned sequence).
-  return base::FeatureList::IsEnabled(kDistinctModuleDatabaseSequence)
-             ? g_distinct_task_runner.Get()
-             : base::CreateSequencedTaskRunner({content::BrowserThread::UI});
+  return g_module_database_task_runner.Get();
 }
 
 // static