[CrOS MultiDevice] Initialize two preference values to true.

This CL updates the kSuiteEnabledPrefName and
kAndroidMessagesFeatureEnabledPrefName preferences to true when they are
registered. These values should be set to true so that once the setup
flow completes, the toggles will be turned on. Without this change,
users would complete the setup flow only to discover that MultiDevice
features are disabled.

Note that this change does not mean that these features will be
available without completing setup; these preferences are not used until
after setup has completed.

Bug: 824568
Change-Id: Ib14434a320a6dc9b1091e8e246f6924835a03763
Reviewed-on: https://chromium-review.googlesource.com/1170176Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582262}

chromeos/services/multidevice_setup/public/cpp/prefs.cc

@@ -36,8 +36,8 @@ const char kInstantTetheringFeatureAllowedPrefName[] = "tether.allowed";
 const char kInstantTetheringFeatureEnabledPrefName[] = "tether.enabled";
 
 void RegisterFeaturePrefs(PrefRegistrySimple* registry) {
-  registry->RegisterBooleanPref(kSuiteEnabledPrefName, false);
-  registry->RegisterBooleanPref(kAndroidMessagesFeatureEnabledPrefName, false);
+  registry->RegisterBooleanPref(kSuiteEnabledPrefName, true);
+  registry->RegisterBooleanPref(kAndroidMessagesFeatureEnabledPrefName, true);
   registry->RegisterBooleanPref(kInstantTetheringFeatureAllowedPrefName, true);
   registry->RegisterBooleanPref(kInstantTetheringFeatureEnabledPrefName, true);
 }