[Tango->FCM] New statuses to allow better identify rediness of the invalidation service.

As of today, no status of the FCMInvalidationService is recorded if
service isn't started. It makes hard to spot the regression, which
happens when invalidation service can't be started. This CL introduces
new statuses, which will be recorded, when invalidation service was
unable to start.

BUG=924957
[email protected]

Change-Id: I5fcca7518df5f933b708cd9d0b31042aed734afd
Reviewed-on: https://chromium-review.googlesource.com/c/1483015
Commit-Queue: Tatiana Gornak <[email protected]>
Reviewed-by: Julian Pastarmov <[email protected]>
Reviewed-by: Jan Krcal <[email protected]>
Cr-Commit-Position: refs/heads/master@{#635084}
diff --git a/components/invalidation/impl/profile_identity_provider.cc b/components/invalidation/impl/profile_identity_provider.cc
index b7dbdb5..2bda764 100644
--- a/components/invalidation/impl/profile_identity_provider.cc
+++ b/components/invalidation/impl/profile_identity_provider.cc
@@ -72,7 +72,7 @@
   return active_account_id_;
 }
 
-bool ProfileIdentityProvider::IsActiveAccountAvailable() {
+bool ProfileIdentityProvider::IsActiveAccountWithRefreshToken() {
   if (GetActiveAccountId().empty() || !identity_manager_ ||
       !identity_manager_->HasAccountWithRefreshToken(GetActiveAccountId()))
     return false;