device/bluetooth: Enable the use of btdispatch by default

This sets the feature flag kNewblue to be enabled by default. The effect
of this is that Chrome will by default communicate to Chrome OS'
Bluetooth dispatcher (btdispatch) instead of BlueZ. Currently,
btdispatch only forwards the D-Bus traffic to BlueZ without NewBlue
enabled.

Bug: 999676
Change-Id: I7089225726ef52c1b8465f3a67b3fdbf01b01882
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1783719Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Sonny Sasaka <sonnysasaka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#693431}

device/base/features.cc

@@ -17,8 +17,7 @@ const base::Feature kNewBLEWinImplementation{"NewBLEWinImplementation",
 
 #if defined(OS_CHROMEOS)
 // Enables or disables the use of newblue Bluetooth daemon on Chrome OS.
-const base::Feature kNewblueDaemon{"Newblue",
-                                   base::FEATURE_DISABLED_BY_DEFAULT};
+const base::Feature kNewblueDaemon{"Newblue", base::FEATURE_ENABLED_BY_DEFAULT};
 #endif  // defined(OS_CHROMEOS)
 
 #if BUILDFLAG(ENABLE_VR)