Don't check TransportState::DISABLED in password_manager_features_util

The check is redundant as it's already implied by IsEngineInitialized().
It's also misleading since the introduction of TransportState::PAUSED in
crrev.com/c/2302149.

Bug: None
Change-Id: I18325269b0a4eee8b011e63588d95e41b404a978
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310335Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Victor Vianna <victorvianna@google.com>
Cr-Commit-Position: refs/heads/master@{#790777}

components/password_manager/core/browser/password_manager_features_util.cc

@@ -55,8 +55,6 @@ bool CanAccountStorageBeEnabled(const syncer::SyncService* sync_service) {
 //   storage).
 bool IsUserEligibleForAccountStorage(const syncer::SyncService* sync_service) {
   return CanAccountStorageBeEnabled(sync_service) &&
-         sync_service->GetTransportState() !=
-             syncer::SyncService::TransportState::DISABLED &&
          sync_service->IsEngineInitialized() &&
          !sync_service->GetUserSettings()->IsUsingSecondaryPassphrase() &&
          !sync_service->IsSyncFeatureEnabled();