[Dice] TiclInvalidationService should start when the user signs in.

If the token service has already a refresh token for the authenticated
account before this account is signed in to Chrome, then |OnRefreshTokenAvailable|
notification will not be called after |OnActiveAccountLogin|.

This CL changes the TiclInvalidationService to handle the case when the
refresh token is already present when |OnActiveAccountLogin| is fired.

See bug for the link to the design document.

Bug: 733226
Change-Id: I205e522ebe75c059b9125e113f451cf328a2f564
Reviewed-on: https://chromium-review.googlesource.com/559537Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487594}

components/invalidation/impl/ticl_invalidation_service.cc

@@ -253,6 +253,11 @@ void TiclInvalidationService::OnGetTokenFailure(
   }
 }
 
+void TiclInvalidationService::OnActiveAccountLogin() {
+  if (!IsStarted() && IsReadyToStart())
+    StartInvalidator(network_channel_type_);
+}
+
 void TiclInvalidationService::OnRefreshTokenAvailable(
     const std::string& account_id) {
   if (!IsStarted() && IsReadyToStart())

components/invalidation/impl/ticl_invalidation_service.h

@@ -98,6 +98,7 @@ class TiclInvalidationService : public InvalidationService,
   void OnRefreshTokenRevoked(const std::string& account_id) override;
 
   // IdentityProvider::Observer implementation.
+  void OnActiveAccountLogin() override;
   void OnActiveAccountLogout() override;
 
   // TiclSettingsProvider::Observer implementation.