[sync] Divorce DataTypeManager from NotificationService notifications by creating a new DataTypeMa…

chrome/common/chrome_notification_types.h

Index: chrome/common/chrome_notification_types.h
diff --git a/chrome/common/chrome_notification_types.h b/chrome/common/chrome_notification_types.h
index 002f93fb1ab7ffe810346bbb4e109d5c14c7907f..aec6e35050f2504bd4df96deaf4d3abcb8a81629 100644
--- a/chrome/common/chrome_notification_types.h
+++ b/chrome/common/chrome_notification_types.h
@@ -811,15 +811,15 @@ enum NotificationType {
 
   // Sync --------------------------------------------------------------------
 
-  // Sent when the syncer is blocked configuring.
-  NOTIFICATION_SYNC_CONFIGURE_BLOCKED,
+  // The sync service has finished the datatype configuration process. The
+  // source is the ProfileSyncService object of the Profile. There are no
+  // details.
+  NOTIFICATION_SYNC_CONFIGURE_DONE,
 
-  // The sync service has started the configuration process.
+  // The sync service has started the datatype configuration process. The source
+  // is the ProfileSyncService object of the Profile. There are no details.
   NOTIFICATION_SYNC_CONFIGURE_START,
 
-  // The sync service is finished the configuration process.
-  NOTIFICATION_SYNC_CONFIGURE_DONE,
-
   // A service is requesting a sync datatype refresh for the current profile.
   // The details value is a const syncer::ModelTypePayloadMap.
   // If the payload map is empty, it should be treated as an invalidation for