[Sync] Add CoreTypes support

chrome/browser/sync/glue/data_type_manager_impl.cc

Index: chrome/browser/sync/glue/data_type_manager_impl.cc
diff --git a/chrome/browser/sync/glue/data_type_manager_impl.cc b/chrome/browser/sync/glue/data_type_manager_impl.cc
index 87daedb47c9aa997169c3e5f450d340c310f5da9..a69eb33722e8d6208d514448fa16e79e95fdd8ef 100644
--- a/chrome/browser/sync/glue/data_type_manager_impl.cc
+++ b/chrome/browser/sync/glue/data_type_manager_impl.cc
@@ -81,6 +81,7 @@ void DataTypeManagerImpl::Configure(syncer::ModelTypeSet desired_types,
   // The list of managed users created by this profile is always synced,
   // but they are not a control type.
   desired_types.Put(syncer::MANAGED_USERS);
+  desired_types.Put(syncer::SYNCED_NOTIFICATIONS);

[tim (not reviewing), 2013/07/15 18:36:17]

We don't enable SYNCED_NOTIFICATIONS on Android, right?

It'd be nice to have a formal notion (and Configure() contract) of core types /
"types that aren't profile sync that we always want to sync", like what is
discussed in the Core Services doc, but this looks good for now.  +rsimha FYI.

[Nicolas Zea, 2013/07/15 22:48:43]

I've gone ahead and created a new notion of CoreTypes and PriorityCoreTypes to
help clean things up. And yeah, on other platforms there won't be a DTC, so the
type will get filtered out by the sync backend registrar.

   ConfigureImpl(desired_types, reason);
 }